Displaying and editing images with depth information

ABSTRACT

The present disclosure generally relates to displaying and editing an image with depth information. In response to an input, an object in the image having a one or more elements in a first depth range is identified. The identified object is then isolated from other elements in the image and displayed separately from the other elements. The isolated object may then be utilized in different applications.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. Non-Provisional App. No. 17/732,191, filed Apr. 28, 2022, entitled “DISPLAYING AND EDITING IMAGES WITH DEPTH INFORMATION”, which is a continuation of U.S. Non-Provisional App. No. 16/528,257, filed Jul. 31, 2019, now U.S. Pat. No. 11,321,857, entitled “DISPLAYING AND EDITING IMAGES WITH DEPTH INFORMATION”, which claims priority to U.S. Provisional App. No. 62/739,131, filed Sep. 28, 2018, entitled “DISPLAYING AND EDITING IMAGES WITH DEPTH INFORMATION”, the contents of which are hereby incorporated by reference in their entireties.

FIELD

The present disclosure relates generally to computer user interfaces, and more specifically to techniques for displaying and editing images with depth information.

BACKGROUND

Users are increasingly using electronic devices to display and edit images. Most electronic devices are capable of displaying a static image for viewing. As an example, some electronic devices provide interactive interfaces to display and edit images.

BRIEF SUMMARY

Some techniques for displaying and editing images using electronic devices, however, are generally cumbersome and inefficient. For example, some existing techniques use a complex and time-consuming user interface, which may include multiple key presses or keystrokes. Existing techniques require more time than necessary, wasting user time and device energy. This latter consideration is particularly important in battery-operated devices.

Accordingly, the present technique provides electronic devices with faster, more efficient methods and interfaces for displaying and editing images. Such methods and interfaces optionally complement or replace other methods for displaying and editing images. Such methods and interfaces reduce the cognitive burden on a user and produce a more efficient human-machine interface. For battery-operated computing devices, such methods and interfaces conserve power and increase the time between battery charges.

In some embodiments, a method is performed at an electronic device with a display. The method includes: receiving a request to display an image that includes a subject, wherein image data associated with the image includes depth information associated with the subject; in response to the request: displaying a first modified image on the display, wherein displaying the first modified image includes displaying, based on the depth information, a first level of simulated lighting on a first portion of the subject and a second level of simulated lighting on a second portion of the subject, the first level being greater than the second level; and subsequent to displaying the first modified image, displaying a second modified image, wherein displaying the second modified image includes displaying, based on the depth information, a third level of simulated lighting on the first portion of the subject and a fourth level of simulated lighting on the second portion of the subject, the fourth level being greater than the second level.

In some embodiments, a non-transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of an electronic device with a display. The one or more programs include instructions for: receiving a request to display an image that includes a subject, wherein image data associated with the image includes depth information associated with the subject; in response to the request: displaying a first modified image on the display, wherein displaying the first modified image includes displaying, based on the depth information, a first level of simulated lighting on a first portion of the subject and a second level of simulated lighting on a second portion of the subject, the first level being greater than the second level; and subsequent to displaying the first modified image, displaying a second modified image, wherein displaying the second modified image includes displaying, based on the depth information, a third level of simulated lighting on the first portion of the subject and a fourth level of simulated lighting on the second portion of the subject, the fourth level being greater than the second level.

In some embodiments, a transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of an electronic device with a display. The one or more programs include instructions for: receiving a request to display an image that includes a subject, wherein image data associated with the image includes depth information associated with the subject; in response to the request: displaying a first modified image on the display, wherein displaying the first modified image includes displaying, based on the depth information, a first level of simulated lighting on a first portion of the subject and a second level of simulated lighting on a second portion of the subject, the first level being greater than the second level; and subsequent to displaying the first modified image, displaying a second modified image, wherein displaying the second modified image includes displaying, based on the depth information, a third level of simulated lighting on the first portion of the subject and a fourth level of simulated lighting on the second portion of the subject, the fourth level being greater than the second level.

In some embodiments, an electronic device includes a display, one or more processors, and memory. The memory stores one or more programs configured to be executed by the one or more processors. The one or more programs including instructions for: receiving a request to display an image that includes a subject, wherein image data associated with the image includes depth information associated with the subject; in response to the request: displaying a first modified image on the display, wherein displaying the first modified image includes displaying, based on the depth information, a first level of simulated lighting on a first portion of the subject and a second level of simulated lighting on a second portion of the subject, the first level being greater than the second level; and subsequent to displaying the first modified image, displaying a second modified image, wherein displaying the second modified image includes displaying, based on the depth information, a third level of simulated lighting on the first portion of the subject and a fourth level of simulated lighting on the second portion of the subject, the fourth level being greater than the second level.

In some embodiments, an electronic device includes: a display; means for receiving a request to display an image that includes a subject, wherein image data associated with the image includes depth information associated with the subject; means for, in response to the request: displaying a first modified image on the display, wherein displaying the first modified image includes displaying, based on the depth information, a first level of simulated lighting on a first portion of the subject and a second level of simulated lighting on a second portion of the subject, the first level being greater than the second level; and subsequent to displaying the first modified image, displaying a second modified image, wherein displaying the second modified image includes displaying, based on the depth information, a third level of simulated lighting on the first portion of the subject and a fourth level of simulated lighting on the second portion of the subject, the fourth level being greater than the second level.

In some embodiments, a method is performed at an electronic device with a display. The method includes: displaying, on the display, an image including a plurality of elements, wherein the plurality of elements are associated with depth information that specifies different depths for different elements in the plurality of elements; while displaying the image on the display, receiving a request to edit a portion of the image; and in response to receiving the request to edit the portion of the image, modifying, based on the depth information, visual characteristics of one or more elements of the plurality of elements in a first depth range without modifying visual characteristics of elements that are not in the first depth range.

In some embodiments, a non-transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of an electronic device with a display. The one or more programs include instructions for: displaying, on the display, an image including a plurality of elements, wherein the plurality of elements are associated with depth information that specifies different depths for different elements in the plurality of elements; while displaying the image on the display, receiving a request to edit a portion of the image; and in response to receiving the request to edit the portion of the image, modifying, based on the depth information, visual characteristics of one or more elements of the plurality of elements in a first depth range without modifying visual characteristics of elements that are not in the first depth range.

In some embodiments, a transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of an electronic device with a display. The one or more programs include instructions for: displaying, on the display, an image including a plurality of elements, wherein the plurality of elements are associated with depth information that specifies different depths for different elements in the plurality of elements; while displaying the image on the display, receiving a request to edit a portion of the image; and in response to receiving the request to edit the portion of the image, modifying, based on the depth information, visual characteristics of one or more elements of the plurality of elements in a first depth range without modifying visual characteristics of elements that are not in the first depth range.

In some embodiments, an electronic device includes a display, one or more processors, and memory. The memory stores one or more programs configured to be executed by the one or more processors. The one or more programs including instructions for: displaying, on the display, an image including a plurality of elements, wherein the plurality of elements are associated with depth information that specifies different depths for different elements in the plurality of elements; while displaying the image on the display, receiving a request to edit a portion of the image; and in response to receiving the request to edit the portion of the image, modifying, based on the depth information, visual characteristics of one or more elements of the plurality of elements in a first depth range without modifying visual characteristics of elements that are not in the first depth range.

In some embodiments, an electronic device includes: a display; means displaying, on the display, an image including a plurality of elements, wherein the plurality of elements are associated with depth information that specifies different depths for different elements in the plurality of elements; means for, while displaying the image on the display, receiving a request to edit a portion of the image; and means for, in response to receiving the request to edit the portion of the image, modifying, based on the depth information, visual characteristics of one or more elements of the plurality of elements in a first depth range without modifying visual characteristics of elements that are not in the first depth range.

Executable instructions for performing these functions are, optionally, included in a non-transitory computer-readable storage medium or other computer program product configured for execution by one or more processors. Executable instructions for performing these functions are, optionally, included in a transitory computer-readable storage medium or other computer program product configured for execution by one or more processors.

Thus, devices are provided with faster, more efficient methods and interfaces for displaying and editing images with depth information, thereby increasing the effectiveness, efficiency, and user satisfaction with such devices. Such methods and interfaces may complement or replace other methods for displaying and editing images.

DESCRIPTION OF THE FIGURES

For a better understanding of the various described embodiments, reference should be made to the Description of Embodiments below, in conjunction with the following drawings in which like reference numerals refer to corresponding parts throughout the figures.

FIG. 1A is a block diagram illustrating a portable multifunction device with a touch-sensitive display in accordance with some embodiments.

FIG. 1B is a block diagram illustrating exemplary components for event handling in accordance with some embodiments.

FIG. 2 illustrates a portable multifunction device having a touch screen in accordance with some embodiments.

FIG. 3 is a block diagram of an exemplary multifunction device with a display and a touch-sensitive surface in accordance with some embodiments.

FIG. 4A illustrates an exemplary user interface for a menu of applications on a portable multifunction device in accordance with some embodiments.

FIG. 4B illustrates an exemplary user interface for a multifunction device with a touch-sensitive surface that is separate from the display in accordance with some embodiments.

FIG. 5A illustrates a personal electronic device in accordance with some embodiments.

FIG. 5B is a block diagram illustrating a personal electronic device in accordance with some embodiments.

FIGS. 5C-5D illustrate exemplary components of a personal electronic device having a touch-sensitive display and intensity sensors in accordance with some embodiments.

FIGS. 5E-5H illustrate exemplary components and user interfaces of a personal electronic device in accordance with some embodiments.

FIGS. 6A-6D illustrate an exemplary technique for applying simulated lighting to an image with depth information in accordance with some embodiments.

FIGS. 7A-7J illustrate exemplary user interfaces for displaying an image with depth information, in accordance with some embodiments.

FIG. 8 is a flow diagram illustrating a method for displaying an image with depth information using an electronic device in accordance with some embodiments.

FIGS. 9A-9K illustrate exemplary user interfaces for editing an image with depth information, in accordance with some embodiments.

FIG. 10 is a flow diagram illustrating a method for editing an image with depth information using an electronic device in accordance with some embodiments.

DESCRIPTION OF EMBODIMENTS

The following description sets forth exemplary methods, parameters, and the like. It should be recognized, however, that such description is not intended as a limitation on the scope of the present disclosure but is instead provided as a description of exemplary embodiments.

There is a need for electronic devices that provide efficient methods and interfaces for displaying and editing images with depth information. Such techniques can reduce the cognitive burden on a user who views or edits the images with depth information, thereby enhancing productivity. Further, such techniques can reduce processor and battery power otherwise wasted on redundant user inputs.

Below, FIGS. 1A-1B, 2, 3, 4A-4B, and 5A-5H provide a description of exemplary devices for performing the techniques for displaying and editing images with depth information. FIGS. 6A-6D illustrate an exemplary technique for applying simulated lighting to images with depth information. FIGS. 7A-7J illustrate exemplary user interfaces for displaying images with depth information. FIG. 8 is a flow diagram illustrating methods of displaying images with depth information in accordance with some embodiments. The user interfaces in FIGS. 7A-7J are used to illustrate the processes described below, including the processes in FIG. 8 . FIGS. 9A-9K illustrate exemplary user interfaces for editing images with depth information. FIG. 10 is a flow diagram illustrating methods of editing images with depth information in accordance with some embodiments. The user interfaces in FIGS. 9A-9K are used to illustrate the processes described below, including the processes in FIG. 10 .

Although the following description uses terms “first,” “second,” etc. to describe various elements, these elements should not be limited by the terms. These terms are only used to distinguish one element from another. For example, a first touch could be termed a second touch, and, similarly, a second touch could be termed a first touch, without departing from the scope of the various described embodiments. The first touch and the second touch are both touches, but they are not the same touch.

The terminology used in the description of the various described embodiments herein is for the purpose of describing particular embodiments only and is not intended to be limiting. As used in the description of the various described embodiments and the appended claims, the singular forms “a,” “an,” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will also be understood that the term “and/or” as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items. It will be further understood that the terms “includes,” “including,” “comprises,” and/or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.

The term “if” is, optionally, construed to mean “when” or “upon” or “in response to determining” or “in response to detecting,” depending on the context. Similarly, the phrase “if it is determined” or “if [a stated condition or event] is detected” is, optionally, construed to mean “upon determining” or “in response to determining” or “upon detecting [the stated condition or event]” or “in response to detecting [the stated condition or event],” depending on the context.

Embodiments of electronic devices, user interfaces for such devices, and associated processes for using such devices are described. In some embodiments, the device is a portable communications device, such as a mobile telephone, that also contains other functions, such as PDA and/or music player functions. Exemplary embodiments of portable multifunction devices include, without limitation, the iPhone®, iPod Touch®, and iPad® devices from Apple Inc. of Cupertino, California. Other portable electronic devices, such as laptops or tablet computers with touch-sensitive surfaces (e.g., touch screen displays and/or touchpads), are, optionally, used. It should also be understood that, in some embodiments, the device is not a portable communications device, but is a desktop computer with a touch-sensitive surface (e.g., a touch screen display and/or a touchpad).

In the discussion that follows, an electronic device that includes a display and a touch-sensitive surface is described. It should be understood, however, that the electronic device optionally includes one or more other physical user-interface devices, such as a physical keyboard, a mouse, and/or a joystick.

The device typically supports a variety of applications, such as one or more of the following: a drawing application, a presentation application, a word processing application, a website creation application, a disk authoring application, a spreadsheet application, a gaming application, a telephone application, a video conferencing application, an e-mail application, an instant messaging application, a workout support application, a photo management application, a digital camera application, a digital video camera application, a web browsing application, a digital music player application, and/or a digital video player application.

The various applications that are executed on the device optionally use at least one common physical user-interface device, such as the touch-sensitive surface. One or more functions of the touch-sensitive surface as well as corresponding information displayed on the device are, optionally, adjusted and/or varied from one application to the next and/or within a respective application. In this way, a common physical architecture (such as the touch-sensitive surface) of the device optionally supports the variety of applications with user interfaces that are intuitive and transparent to the user.

Attention is now directed toward embodiments of portable devices with touch-sensitive displays. FIG. 1A is a block diagram illustrating portable multifunction device 100 with touch-sensitive display system 112 in accordance with some embodiments. Touch-sensitive display 112 is sometimes called a “touch screen” for convenience and is sometimes known as or called a “touch-sensitive display system.” Device 100 includes memory 102 (which optionally includes one or more computer-readable storage mediums), memory controller 122, one or more processing units (CPUs) 120, peripherals interface 118, RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, input/output (I/O) subsystem 106, other input control devices 116, and external port 124. Device 100 optionally includes one or more optical sensors 164. Device 100 optionally includes one or more contact intensity sensors 165 for detecting intensity of contacts on device 100 (e.g., a touch-sensitive surface such as touch-sensitive display system 112 of device 100). Device 100 optionally includes one or more tactile output generators 167 for generating tactile outputs on device 100 (e.g., generating tactile outputs on a touch-sensitive surface such as touch-sensitive display system 112 of device 100 or touchpad 355 of device 300). These components optionally communicate over one or more communication buses or signal lines 103.

As used in the specification and claims, the term “intensity” of a contact on a touch-sensitive surface refers to the force or pressure (force per unit area) of a contact (e.g., a finger contact) on the touch-sensitive surface, or to a substitute (proxy) for the force or pressure of a contact on the touch-sensitive surface. The intensity of a contact has a range of values that includes at least four distinct values and more typically includes hundreds of distinct values (e.g., at least 256). Intensity of a contact is, optionally, determined (or measured) using various approaches and various sensors or combinations of sensors. For example, one or more force sensors underneath or adjacent to the touch-sensitive surface are, optionally, used to measure force at various points on the touch-sensitive surface. In some implementations, force measurements from multiple force sensors are combined (e.g., a weighted average) to determine an estimated force of a contact. Similarly, a pressure-sensitive tip of a stylus is, optionally, used to determine a pressure of the stylus on the touch-sensitive surface. Alternatively, the size of the contact area detected on the touch-sensitive surface and/or changes thereto, the capacitance of the touch-sensitive surface proximate to the contact and/or changes thereto, and/or the resistance of the touch-sensitive surface proximate to the contact and/or changes thereto are, optionally, used as a substitute for the force or pressure of the contact on the touch-sensitive surface. In some implementations, the substitute measurements for contact force or pressure are used directly to determine whether an intensity threshold has been exceeded (e.g., the intensity threshold is described in units corresponding to the substitute measurements). In some implementations, the substitute measurements for contact force or pressure are converted to an estimated force or pressure, and the estimated force or pressure is used to determine whether an intensity threshold has been exceeded (e.g., the intensity threshold is a pressure threshold measured in units of pressure). Using the intensity of a contact as an attribute of a user input allows for user access to additional device functionality that may otherwise not be accessible by the user on a reduced-size device with limited real estate for displaying affordances (e.g., on a touch-sensitive display) and/or receiving user input (e.g., via a touch-sensitive display, a touch-sensitive surface, or a physical/mechanical control such as a knob or a button).

As used in the specification and claims, the term “tactile output” refers to physical displacement of a device relative to a previous position of the device, physical displacement of a component (e.g., a touch-sensitive surface) of a device relative to another component (e.g., housing) of the device, or displacement of the component relative to a center of mass of the device that will be detected by a user with the user’s sense of touch. For example, in situations where the device or the component of the device is in contact with a surface of a user that is sensitive to touch (e.g., a finger, palm, or other part of a user’s hand), the tactile output generated by the physical displacement will be interpreted by the user as a tactile sensation corresponding to a perceived change in physical characteristics of the device or the component of the device. For example, movement of a touch-sensitive surface (e.g., a touch-sensitive display or trackpad) is, optionally, interpreted by the user as a “down click” or “up click” of a physical actuator button. In some cases, a user will feel a tactile sensation such as an “down click” or “up click” even when there is no movement of a physical actuator button associated with the touch-sensitive surface that is physically pressed (e.g., displaced) by the user’s movements. As another example, movement of the touch-sensitive surface is, optionally, interpreted or sensed by the user as “roughness” of the touch-sensitive surface, even when there is no change in smoothness of the touch-sensitive surface. While such interpretations of touch by a user will be subject to the individualized sensory perceptions of the user, there are many sensory perceptions of touch that are common to a large majority of users. Thus, when a tactile output is described as corresponding to a particular sensory perception of a user (e.g., an “up click,” a “down click,” “roughness”), unless otherwise stated, the generated tactile output corresponds to physical displacement of the device or a component thereof that will generate the described sensory perception for a typical (or average) user.

It should be appreciated that device 100 is only one example of a portable multifunction device, and that device 100 optionally has more or fewer components than shown, optionally combines two or more components, or optionally has a different configuration or arrangement of the components. The various components shown in FIG. 1A are implemented in hardware, software, or a combination of both hardware and software, including one or more signal processing and/or application-specific integrated circuits.

Memory 102 optionally includes high-speed random access memory and optionally also includes non-volatile memory, such as one or more magnetic disk storage devices, flash memory devices, or other non-volatile solid-state memory devices. Memory controller 122 optionally controls access to memory 102 by other components of device 100.

Peripherals interface 118 can be used to couple input and output peripherals of the device to CPU 120 and memory 102. The one or more processors 120 run or execute various software programs and/or sets of instructions stored in memory 102 to perform various functions for device 100 and to process data. In some embodiments, peripherals interface 118, CPU 120, and memory controller 122 are, optionally, implemented on a single chip, such as chip 104. In some other embodiments, they are, optionally, implemented on separate chips.

RF (radio frequency) circuitry 108 receives and sends RF signals, also called electromagnetic signals. RF circuitry 108 converts electrical signals to/from electromagnetic signals and communicates with communications networks and other communications devices via the electromagnetic signals. RF circuitry 108 optionally includes well-known circuitry for performing these functions, including but not limited to an antenna system, an RF transceiver, one or more amplifiers, a tuner, one or more oscillators, a digital signal processor, a CODEC chipset, a subscriber identity module (SIM) card, memory, and so forth. RF circuitry 108 optionally communicates with networks, such as the Internet, also referred to as the World Wide Web (WWW), an intranet and/or a wireless network, such as a cellular telephone network, a wireless local area network (LAN) and/or a metropolitan area network (MAN), and other devices by wireless communication. The RF circuitry 108 optionally includes well-known circuitry for detecting near field communication (NFC) fields, such as by a short-range communication radio. The wireless communication optionally uses any of a plurality of communications standards, protocols, and technologies, including but not limited to Global System for Mobile Communications (GSM), Enhanced Data GSM Environment (EDGE), high-speed downlink packet access (HSDPA), high-speed uplink packet access (HSUPA), Evolution, Data-Only (EV-DO), HSPA, HSPA+, Dual-Cell HSPA (DC-HSPDA), long term evolution (LTE), near field communication (NFC), wideband code division multiple access (W-CDMA), code division multiple access (CDMA), time division multiple access (TDMA), Bluetooth, Bluetooth Low Energy (BTLE), Wireless Fidelity (Wi-Fi) (e.g., IEEE 802.1 1a, IEEE 802.1 1b, IEEE 802.11 g, IEEE 802.11n, and/or IEEE 802.1 1ac), voice over Internet Protocol (VoIP), Wi-MAX, a protocol for e-mail (e.g., Internet message access protocol (IMAP) and/or post office protocol (POP)), instant messaging (e.g., extensible messaging and presence protocol (XMPP), Session Initiation Protocol for Instant Messaging and Presence Leveraging Extensions (SIMPLE), Instant Messaging and Presence Service (IMPS)), and/or Short Message Service (SMS), or any other suitable communication protocol, including communication protocols not yet developed as of the filing date of this document.

Audio circuitry 110, speaker 111, and microphone 113 provide an audio interface between a user and device 100. Audio circuitry 110 receives audio data from peripherals interface 118, converts the audio data to an electrical signal, and transmits the electrical signal to speaker 111. Speaker 111 converts the electrical signal to human-audible sound waves. Audio circuitry 110 also receives electrical signals converted by microphone 113 from sound waves. Audio circuitry 110 converts the electrical signal to audio data and transmits the audio data to peripherals interface 118 for processing. Audio data is, optionally, retrieved from and/or transmitted to memory 102 and/or RF circuitry 108 by peripherals interface 118. In some embodiments, audio circuitry 110 also includes a headset jack (e.g., 212, FIG. 2 ). The headset jack provides an interface between audio circuitry 110 and removable audio input/output peripherals, such as output-only headphones or a headset with both output (e.g., a headphone for one or both ears) and input (e.g., a microphone).

I/O subsystem 106 couples input/output peripherals on device 100, such as touch screen 112 and other input control devices 116, to peripherals interface 118. I/O subsystem 106 optionally includes display controller 156, optical sensor controller 158, depth camera controller 169, intensity sensor controller 159, haptic feedback controller 161, and one or more input controllers 160 for other input or control devices. The one or more input controllers 160 receive/send electrical signals from/to other input control devices 116. The other input control devices 116 optionally include physical buttons (e.g., push buttons, rocker buttons, etc.), dials, slider switches, joysticks, click wheels, and so forth. In some alternate embodiments, input controller(s) 160 are, optionally, coupled to any (or none) of the following: a keyboard, an infrared port, a USB port, and a pointer device such as a mouse. The one or more buttons (e.g., 208, FIG. 2 ) optionally include an up/down button for volume control of speaker 111 and/or microphone 113. The one or more buttons optionally include a push button (e.g., 206, FIG. 2 ).

A quick press of the push button optionally disengages a lock of touch screen 112 or optionally begins a process that uses gestures on the touch screen to unlock the device, as described in U.S. Pat. App. 11/322,549, “Unlocking a Device by Performing Gestures on an Unlock Image,” filed Dec. 23, 2005, U.S. Pat. No. 7,657,849, which is hereby incorporated by reference in its entirety. A longer press of the push button (e.g., 206) optionally turns power to device 100 on or off. The functionality of one or more of the buttons are, optionally, user-customizable. Touch screen 112 is used to implement virtual or soft buttons and one or more soft keyboards.

Touch-sensitive display 112 provides an input interface and an output interface between the device and a user. Display controller 156 receives and/or sends electrical signals from/to touch screen 112. Touch screen 112 displays visual output to the user. The visual output optionally includes graphics, text, icons, video, and any combination thereof (collectively termed “graphics”). In some embodiments, some or all of the visual output optionally corresponds to user-interface objects.

Touch screen 112 has a touch-sensitive surface, sensor, or set of sensors that accepts input from the user based on haptic and/or tactile contact. Touch screen 112 and display controller 156 (along with any associated modules and/or sets of instructions in memory 102) detect contact (and any movement or breaking of the contact) on touch screen 112 and convert the detected contact into interaction with user-interface objects (e.g., one or more soft keys, icons, web pages, or images) that are displayed on touch screen 112. In an exemplary embodiment, a point of contact between touch screen 112 and the user corresponds to a finger of the user.

Touch screen 112 optionally uses LCD (liquid crystal display) technology, LPD (light emitting polymer display) technology, or LED (light emitting diode) technology, although other display technologies are used in other embodiments. Touch screen 112 and display controller 156 optionally detect contact and any movement or breaking thereof using any of a plurality of touch sensing technologies now known or later developed, including but not limited to capacitive, resistive, infrared, and surface acoustic wave technologies, as well as other proximity sensor arrays or other elements for determining one or more points of contact with touch screen 112. In an exemplary embodiment, projected mutual capacitance sensing technology is used, such as that found in the iPhone® and iPod Touch® from Apple Inc. of Cupertino, California.

A touch-sensitive display in some embodiments of touch screen 112 is, optionally, analogous to the multi-touch sensitive touchpads described in the following U.S. Pats: 6,323,846 (Westerman et al.), 6,570,557 (Westerman et al.), and/or 6,677,932 (Westerman), and/or U.S. Pat. Publication 2002/0015024A1, each of which is hereby incorporated by reference in its entirety. However, touch screen 112 displays visual output from device 100, whereas touch-sensitive touchpads do not provide visual output.

A touch-sensitive display in some embodiments of touch screen 112 is described in the following applications: (1) U.S. Pat. App. No. 11/381,313, “Multipoint Touch Surface Controller,” filed May 2, 2006; (2) U.S. Pat. App. No. 10/840,862, “Multipoint Touchscreen,” filed May 6, 2004; (3) U.S. Pat. App. No. 10/903,964, “Gestures For Touch Sensitive Input Devices,” filed Jul. 30, 2004; (4) U.S. Pat. App. No. 11/048,264, “Gestures For Touch Sensitive Input Devices,” filed Jan. 31, 2005; (5) U.S. Pat. App. No. 11/038,590, “Mode-Based Graphical User Interfaces For Touch Sensitive Input Devices,” filed Jan. 18, 2005; (6) U.S. Pat. App. No. 11/228,758, “Virtual Input Device Placement On A Touch Screen User Interface,” filed Sep. 16, 2005; (7) U.S. Pat. App. No. 11/228,700, “Operation Of A Computer With A Touch Screen Interface,” filed Sep. 16, 2005; (8) U.S. Pat. App. No. 11/228,737, “Activating Virtual Keys Of A Touch-Screen Virtual Keyboard,” filed Sep. 16, 2005; and (9) U.S. Pat. App. No. 11/367,749, “Multi-Functional Hand-Held Device,” filed Mar. 3, 2006. All of these applications are incorporated by reference herein in their entirety.

Touch screen 112 optionally has a video resolution in excess of 100 dpi. In some embodiments, the touch screen has a video resolution of approximately 160 dpi. The user optionally makes contact with touch screen 112 using any suitable object or appendage, such as a stylus, a finger, and so forth. In some embodiments, the user interface is designed to work primarily with finger-based contacts and gestures, which can be less precise than stylus-based input due to the larger area of contact of a finger on the touch screen. In some embodiments, the device translates the rough finger-based input into a precise pointer/cursor position or command for performing the actions desired by the user.

In some embodiments, in addition to the touch screen, device 100 optionally includes a touchpad for activating or deactivating particular functions. In some embodiments, the touchpad is a touch-sensitive area of the device that, unlike the touch screen, does not display visual output. The touchpad is, optionally, a touch-sensitive surface that is separate from touch screen 112 or an extension of the touch-sensitive surface formed by the touch screen.

Device 100 also includes power system 162 for powering the various components. Power system 162 optionally includes a power management system, one or more power sources (e.g., battery, alternating current (AC)), a recharging system, a power failure detection circuit, a power converter or inverter, a power status indicator (e.g., a light-emitting diode (LED)) and any other components associated with the generation, management and distribution of power in portable devices.

Device 100 optionally also includes one or more optical sensors 164. FIG. 1A shows an optical sensor coupled to optical sensor controller 158 in I/O subsystem 106. Optical sensor 164 optionally includes charge-coupled device (CCD) or complementary metal-oxide semiconductor (CMOS) phototransistors. Optical sensor 164 receives light from the environment, projected through one or more lenses, and converts the light to data representing an image. In conjunction with imaging module 143 (also called a camera module), optical sensor 164 optionally captures still images or video. In some embodiments, an optical sensor is located on the back of device 100, opposite touch screen display 112 on the front of the device so that the touch screen display is enabled for use as a viewfinder for still and/or video image acquisition. In some embodiments, an optical sensor is located on the front of the device so that the user’s image is, optionally, obtained for video conferencing while the user views the other video conference participants on the touch screen display. In some embodiments, the position of optical sensor 164 can be changed by the user (e.g., by rotating the lens and the sensor in the device housing) so that a single optical sensor 164 is used along with the touch screen display for both video conferencing and still and/or video image acquisition.

Device 100 optionally also includes one or more depth camera sensors 175. FIG. 1A shows a depth camera sensor coupled to depth camera controller 169 in I/O subsystem 106. Depth camera sensor 175 receives data from the environment to create a three dimensional model of an object (e.g., a face) within a scene from a viewpoint (e.g., a depth camera sensor). In some embodiments, in conjunction with imaging module 143 (also called a camera module), depth camera sensor 175 is optionally used to determine a depth map of different portions of an image captured by the imaging module 143. In some embodiments, a depth camera sensor is located on the front of device 100 so that the user’s image with depth information is, optionally, obtained for video conferencing while the user views the other video conference participants on the touch screen display and to capture selfies with depth map data. In some embodiments, the depth camera sensor 175 is located on the back of device, or on the back and the front of the device 100. In some embodiments, the position of depth camera sensor 175 can be changed by the user (e.g., by rotating the lens and the sensor in the device housing) so that a depth camera sensor 175 is used along with the touch screen display for both video conferencing and still and/or video image acquisition.

In some embodiments, a depth map (e.g., depth map image) contains information (e.g., values) that relates to the distance of objects in a scene from a viewpoint (e.g., a camera, an optical sensor, a depth camera sensor). In one embodiment of a depth map, each depth pixel defines the position in the viewpoint’s Z-axis where its corresponding two-dimensional pixel is located. In some embodiments, a depth map is composed of pixels wherein each pixel is defined by a value (e.g., 0 - 255). For example, the “0” value represents pixels that are located at the most distant place in a “three dimensional” scene and the “255” value represents pixels that are located closest to a viewpoint (e.g., a camera, an optical sensor, a depth camera sensor) in the “three dimensional” scene. In other embodiments, a depth map represents the distance between an object in a scene and the plane of the viewpoint. In some embodiments, the depth map includes information about the relative depth of various features of an object of interest in view of the depth camera (e.g., the relative depth of eyes, nose, mouth, ears of a user’s face). In some embodiments, the depth map includes information that enables the device to determine contours of the object of interest in a z direction.

Device 100 optionally also includes one or more contact intensity sensors 165. FIG. 1A shows a contact intensity sensor coupled to intensity sensor controller 159 in I/O subsystem 106. Contact intensity sensor 165 optionally includes one or more piezoresistive strain gauges, capacitive force sensors, electric force sensors, piezoelectric force sensors, optical force sensors, capacitive touch-sensitive surfaces, or other intensity sensors (e.g., sensors used to measure the force (or pressure) of a contact on a touch-sensitive surface). Contact intensity sensor 165 receives contact intensity information (e.g., pressure information or a proxy for pressure information) from the environment. In some embodiments, at least one contact intensity sensor is collocated with, or proximate to, a touch-sensitive surface (e.g., touch-sensitive display system 112). In some embodiments, at least one contact intensity sensor is located on the back of device 100, opposite touch screen display 112, which is located on the front of device 100.

Device 100 optionally also includes one or more proximity sensors 166. FIG. 1A shows proximity sensor 166 coupled to peripherals interface 118. Alternately, proximity sensor 166 is, optionally, coupled to input controller 160 in I/O subsystem 106. Proximity sensor 166 optionally performs as described in U.S. Pat. App. Nos. 11/241,839, “Proximity Detector In Handheld Device”; 11/240,788, “Proximity Detector In Handheld Device”; 11/620,702, “Using Ambient Light Sensor To Augment Proximity Sensor Output”; 11/586,862, “Automated Response To And Sensing Of User Activity In Portable Devices”; and 11/638,251, “Methods And Systems For Automatic Configuration Of Peripherals,” which are hereby incorporated by reference in their entirety. In some embodiments, the proximity sensor turns off and disables touch screen 112 when the multifunction device is placed near the user’s ear (e.g., when the user is making a phone call).

Device 100 optionally also includes one or more tactile output generators 167. FIG. 1A shows a tactile output generator coupled to haptic feedback controller 161 in I/O subsystem 106. Tactile output generator 167 optionally includes one or more electroacoustic devices such as speakers or other audio components and/or electromechanical devices that convert energy into linear motion such as a motor, solenoid, electroactive polymer, piezoelectric actuator, electrostatic actuator, or other tactile output generating component (e.g., a component that converts electrical signals into tactile outputs on the device). Contact intensity sensor 165 receives tactile feedback generation instructions from haptic feedback module 133 and generates tactile outputs on device 100 that are capable of being sensed by a user of device 100. In some embodiments, at least one tactile output generator is collocated with, or proximate to, a touch-sensitive surface (e.g., touch-sensitive display system 112) and, optionally, generates a tactile output by moving the touch-sensitive surface vertically (e.g., in/out of a surface of device 100) or laterally (e.g., back and forth in the same plane as a surface of device 100). In some embodiments, at least one tactile output generator sensor is located on the back of device 100, opposite touch screen display 112, which is located on the front of device 100.

Device 100 optionally also includes one or more accelerometers 168. FIG. 1A shows accelerometer 168 coupled to peripherals interface 118. Alternately, accelerometer 168 is, optionally, coupled to an input controller 160 in I/O subsystem 106. Accelerometer 168 optionally performs as described in U.S. Pat. Publication No. 20050190059, “Acceleration-based Theft Detection System for Portable Electronic Devices,” and U.S. Pat. Publication No. 20060017692, “Methods And Apparatuses For Operating A Portable Device Based On An Accelerometer,” both of which are incorporated by reference herein in their entirety. In some embodiments, information is displayed on the touch screen display in a portrait view or a landscape view based on an analysis of data received from the one or more accelerometers. Device 100 optionally includes, in addition to accelerometer(s) 168, a magnetometer and a GPS (or GLONASS or other global navigation system) receiver for obtaining information concerning the location and orientation (e.g., portrait or landscape) of device 100.

In some embodiments, the software components stored in memory 102 include operating system 126, communication module (or set of instructions) 128, contact/motion module (or set of instructions) 130, graphics module (or set of instructions) 132, text input module (or set of instructions) 134, Global Positioning System (GPS) module (or set of instructions) 135, and applications (or sets of instructions) 136. Furthermore, in some embodiments, memory 102 (FIG. 1A) or 370 (FIG. 3 ) stores device/global internal state 157, as shown in FIGS. 1A and 3 . Device/global internal state 157 includes one or more of: active application state, indicating which applications, if any, are currently active; display state, indicating what applications, views or other information occupy various regions of touch screen display 112; sensor state, including information obtained from the device’s various sensors and input control devices 116; and location information concerning the device’s location and/or attitude.

Operating system 126 (e.g., Darwin, RTXC, LINUX, UNIX, OS X, iOS, WINDOWS, or an embedded operating system such as VxWorks) includes various software components and/or drivers for controlling and managing general system tasks (e.g., memory management, storage device control, power management, etc.) and facilitates communication between various hardware and software components.

Communication module 128 facilitates communication with other devices over one or more external ports 124 and also includes various software components for handling data received by RF circuitry 108 and/or external port 124. External port 124 (e.g., Universal Serial Bus (USB), FIREWIRE, etc.) is adapted for coupling directly to other devices or indirectly over a network (e.g., the Internet, wireless LAN, etc.). In some embodiments, the external port is a multi-pin (e.g., 30-pin) connector that is the same as, or similar to and/or compatible with, the 30-pin connector used on iPod® (trademark of Apple Inc.) devices.

Contact/motion module 130 optionally detects contact with touch screen 112 (in conjunction with display controller 156) and other touch-sensitive devices (e.g., a touchpad or physical click wheel). Contact/motion module 130 includes various software components for performing various operations related to detection of contact, such as determining if contact has occurred (e.g., detecting a finger-down event), determining an intensity of the contact (e.g., the force or pressure of the contact or a substitute for the force or pressure of the contact), determining if there is movement of the contact and tracking the movement across the touch-sensitive surface (e.g., detecting one or more finger-dragging events), and determining if the contact has ceased (e.g., detecting a finger-up event or a break in contact). Contact/motion module 130 receives contact data from the touch-sensitive surface. Determining movement of the point of contact, which is represented by a series of contact data, optionally includes determining speed (magnitude), velocity (magnitude and direction), and/or an acceleration (a change in magnitude and/or direction) of the point of contact. These operations are, optionally, applied to single contacts (e.g., one finger contacts) or to multiple simultaneous contacts (e.g., “multitouch″/multiple finger contacts). In some embodiments, contact/motion module 130 and display controller 156 detect contact on a touchpad.

In some embodiments, contact/motion module 130 uses a set of one or more intensity thresholds to determine whether an operation has been performed by a user (e.g., to determine whether a user has “clicked” on an icon). In some embodiments, at least a subset of the intensity thresholds are determined in accordance with software parameters (e.g., the intensity thresholds are not determined by the activation thresholds of particular physical actuators and can be adjusted without changing the physical hardware of device 100). For example, a mouse “click” threshold of a trackpad or touch screen display can be set to any of a large range of predefined threshold values without changing the trackpad or touch screen display hardware. Additionally, in some implementations, a user of the device is provided with software settings for adjusting one or more of the set of intensity thresholds (e.g., by adjusting individual intensity thresholds and/or by adjusting a plurality of intensity thresholds at once with a system-level click “intensity” parameter).

Contact/motion module 130 optionally detects a gesture input by a user. Different gestures on the touch-sensitive surface have different contact patterns (e.g., different motions, timings, and/or intensities of detected contacts). Thus, a gesture is, optionally, detected by detecting a particular contact pattern. For example, detecting a finger tap gesture includes detecting a finger-down event followed by detecting a finger-up (liftoff) event at the same position (or substantially the same position) as the finger-down event (e.g., at the position of an icon). As another example, detecting a finger swipe gesture on the touch-sensitive surface includes detecting a finger-down event followed by detecting one or more finger-dragging events, and subsequently followed by detecting a finger-up (liftoff) event.

Graphics module 132 includes various known software components for rendering and displaying graphics on touch screen 112 or other display, including components for changing the visual impact (e.g., brightness, transparency, saturation, contrast, or other visual property) of graphics that are displayed. As used herein, the term “graphics” includes any object that can be displayed to a user, including, without limitation, text, web pages, icons (such as user-interface objects including soft keys), digital images, videos, animations, and the like.

In some embodiments, graphics module 132 stores data representing graphics to be used. Each graphic is, optionally, assigned a corresponding code. Graphics module 132 receives, from applications etc., one or more codes specifying graphics to be displayed along with, if necessary, coordinate data and other graphic property data, and then generates screen image data to output to display controller 156.

Haptic feedback module 133 includes various software components for generating instructions used by tactile output generator(s) 167 to produce tactile outputs at one or more locations on device 100 in response to user interactions with device 100.

Text input module 134, which is, optionally, a component of graphics module 132, provides soft keyboards for entering text in various applications (e.g., contacts 137, e-mail 140, IM 141, browser 147, and any other application that needs text input).

GPS module 135 determines the location of the device and provides this information for use in various applications (e.g., to telephone 138 for use in location-based dialing; to camera 143 as picture/video metadata; and to applications that provide location-based services such as weather widgets, local yellow page widgets, and map/navigation widgets).

Applications 136 optionally include the following modules (or sets of instructions), or a subset or superset thereof:

-   Contacts module 137 (sometimes called an address book or contact     list); -   Telephone module 138; -   Video conference module 139; -   E-mail client module 140; -   Instant messaging (IM) module 141; -   Workout support module 142; -   Camera module 143 for still and/or video images; -   Image management module 144; -   Video player module; -   Music player module; -   Browser module 147; -   Calendar module 148; -   Widget modules 149, which optionally include one or more of: weather     widget 149-1, stocks widget 149-2, calculator widget 149-3, alarm     clock widget 149-4, dictionary widget 149-5, and other widgets     obtained by the user, as well as user-created widgets 149-6; -   Widget creator module 150 for making user-created widgets 149-6; -   Search module 151; -   Video and music player module 152, which merges video player module     and music player module; -   Notes module 153; -   Map module 154; and/or -   Online video module 155.

Examples of other applications 136 that are, optionally, stored in memory 102 include other word processing applications, other image editing applications, drawing applications, presentation applications, JAVA-enabled applications, encryption, digital rights management, voice recognition, and voice replication.

In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, contacts module 137 are, optionally, used to manage an address book or contact list (e.g., stored in application internal state 192 of contacts module 137 in memory 102 or memory 370), including: adding name(s) to the address book; deleting name(s) from the address book; associating telephone number(s), e-mail address(es), physical address(es) or other information with a name; associating an image with a name; categorizing and sorting names; providing telephone numbers or e-mail addresses to initiate and/or facilitate communications by telephone 138, video conference module 139, e-mail 140, or IM 141; and so forth.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, telephone module 138 are optionally, used to enter a sequence of characters corresponding to a telephone number, access one or more telephone numbers in contacts module 137, modify a telephone number that has been entered, dial a respective telephone number, conduct a conversation, and disconnect or hang up when the conversation is completed. As noted above, the wireless communication optionally uses any of a plurality of communications standards, protocols, and technologies.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch screen 112, display controller 156, optical sensor 164, optical sensor controller 158, contact/motion module 130, graphics module 132, text input module 134, contacts module 137, and telephone module 138, video conference module 139 includes executable instructions to initiate, conduct, and terminate a video conference between a user and one or more other participants in accordance with user instructions.

In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, e-mail client module 140 includes executable instructions to create, send, receive, and manage e-mail in response to user instructions. In conjunction with image management module 144, e-mail client module 140 makes it very easy to create and send e-mails with still or video images taken with camera module 143.

In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, the instant messaging module 141 includes executable instructions to enter a sequence of characters corresponding to an instant message, to modify previously entered characters, to transmit a respective instant message (for example, using a Short Message Service (SMS) or Multimedia Message Service (MMS) protocol for telephony-based instant messages or using XMPP, SIMPLE, or IMPS for Internet-based instant messages), to receive instant messages, and to view received instant messages. In some embodiments, transmitted and/or received instant messages optionally include graphics, photos, audio files, video files and/or other attachments as are supported in an MMS and/or an Enhanced Messaging Service (EMS). As used herein, “instant messaging” refers to both telephony-based messages (e.g., messages sent using SMS or MMS) and Internet-based messages (e.g., messages sent using XMPP, SIMPLE, or IMPS).

In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, GPS module 135, map module 154, and music player module, workout support module 142 includes executable instructions to create workouts (e.g., with time, distance, and/or calorie burning goals); communicate with workout sensors (sports devices); receive workout sensor data; calibrate sensors used to monitor a workout; select and play music for a workout; and display, store, and transmit workout data.

In conjunction with touch screen 112, display controller 156, optical sensor(s) 164, optical sensor controller 158, contact/motion module 130, graphics module 132, and image management module 144, camera module 143 includes executable instructions to capture still images or video (including a video stream) and store them into memory 102, modify characteristics of a still image or video, or delete a still image or video from memory 102.

In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, and camera module 143, image management module 144 includes executable instructions to arrange, modify (e.g., edit), or otherwise manipulate, label, delete, present (e.g., in a digital slide show or album), and store still and/or video images.

In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, browser module 147 includes executable instructions to browse the Internet in accordance with user instructions, including searching, linking to, receiving, and displaying web pages or portions thereof, as well as attachments and other files linked to web pages.

In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, e-mail client module 140, and browser module 147, calendar module 148 includes executable instructions to create, display, modify, and store calendars and data associated with calendars (e.g., calendar entries, to-do lists, etc.) in accordance with user instructions.

In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, and browser module 147, widget modules 149 are mini-applications that are, optionally, downloaded and used by a user (e.g., weather widget 149-1, stocks widget 149-2, calculator widget 149-3, alarm clock widget 149-4, and dictionary widget 149-5) or created by the user (e.g., user-created widget 149-6). In some embodiments, a widget includes an HTML (Hypertext Markup Language) file, a CSS (Cascading Style Sheets) file, and a JavaScript file. In some embodiments, a widget includes an XML (Extensible Markup Language) file and a JavaScript file (e.g., Yahoo! Widgets).

In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, and browser module 147, the widget creator module 150 are, optionally, used by a user to create widgets (e.g., turning a user-specified portion of a web page into a widget).

In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, search module 151 includes executable instructions to search for text, music, sound, image, video, and/or other files in memory 102 that match one or more search criteria (e.g., one or more user-specified search terms) in accordance with user instructions.

In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, and browser module 147, video and music player module 152 includes executable instructions that allow the user to download and play back recorded music and other sound files stored in one or more file formats, such as MP3 or AAC files, and executable instructions to display, present, or otherwise play back videos (e.g., on touch screen 112 or on an external, connected display via external port 124). In some embodiments, device 100 optionally includes the functionality of an MP3 player, such as an iPod (trademark of Apple Inc.).

In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, notes module 153 includes executable instructions to create and manage notes, to-do lists, and the like in accordance with user instructions.

In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, GPS module 135, and browser module 147, map module 154 are, optionally, used to receive, display, modify, and store maps and data associated with maps (e.g., driving directions, data on stores and other points of interest at or near a particular location, and other location-based data) in accordance with user instructions.

In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, text input module 134, e-mail client module 140, and browser module 147, online video module 155 includes instructions that allow the user to access, browse, receive (e.g., by streaming and/or download), play back (e.g., on the touch screen or on an external, connected display via external port 124), send an e-mail with a link to a particular online video, and otherwise manage online videos in one or more file formats, such as H.264. In some embodiments, instant messaging module 141, rather than e-mail client module 140, is used to send a link to a particular online video. Additional description of the online video application can be found in U.S. Provisional Pat. App. No. 60/936,562, “Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos,” filed Jun. 20, 2007, and U.S. Pat. App. No. 11/968,067, “Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos,” filed Dec. 31, 2007, the contents of which are hereby incorporated by reference in their entirety.

Each of the above-identified modules and applications corresponds to a set of executable instructions for performing one or more functions described above and the methods described in this application (e.g., the computer-implemented methods and other information processing methods described herein). These modules (e.g., sets of instructions) need not be implemented as separate software programs, procedures, or modules, and thus various subsets of these modules are, optionally, combined or otherwise rearranged in various embodiments. For example, video player module is, optionally, combined with music player module into a single module (e.g., video and music player module 152, FIG. 1A). In some embodiments, memory 102 optionally stores a subset of the modules and data structures identified above. Furthermore, memory 102 optionally stores additional modules and data structures not described above.

In some embodiments, device 100 is a device where operation of a predefined set of functions on the device is performed exclusively through a touch screen and/or a touchpad. By using a touch screen and/or a touchpad as the primary input control device for operation of device 100, the number of physical input control devices (such as push buttons, dials, and the like) on device 100 is, optionally, reduced.

The predefined set of functions that are performed exclusively through a touch screen and/or a touchpad optionally include navigation between user interfaces. In some embodiments, the touchpad, when touched by the user, navigates device 100 to a main, home, or root menu from any user interface that is displayed on device 100. In such embodiments, a “menu button” is implemented using a touchpad. In some other embodiments, the menu button is a physical push button or other physical input control device instead of a touchpad.

FIG. 1B is a block diagram illustrating exemplary components for event handling in accordance with some embodiments. In some embodiments, memory 102 (FIG. 1A) or 370 (FIG. 3 ) includes event sorter 170 (e.g., in operating system 126) and a respective application 136-1 (e.g., any of the aforementioned applications 137-151, 155, 380-390).

Event sorter 170 receives event information and determines the application 136-1 and application view 191 of application 136-1 to which to deliver the event information. Event sorter 170 includes event monitor 171 and event dispatcher module 174. In some embodiments, application 136-1 includes application internal state 192, which indicates the current application view(s) displayed on touch-sensitive display 112 when the application is active or executing. In some embodiments, device/global internal state 157 is used by event sorter 170 to determine which application(s) is (are) currently active, and application internal state 192 is used by event sorter 170 to determine application views 191 to which to deliver event information.

In some embodiments, application internal state 192 includes additional information, such as one or more of: resume information to be used when application 136-1 resumes execution, user interface state information that indicates information being displayed or that is ready for display by application 136-1, a state queue for enabling the user to go back to a prior state or view of application 136-1, and a redo/undo queue of previous actions taken by the user.

Event monitor 171 receives event information from peripherals interface 118. Event information includes information about a sub-event (e.g., a user touch on touch-sensitive display 112, as part of a multi-touch gesture). Peripherals interface 118 transmits information it receives from I/O subsystem 106 or a sensor, such as proximity sensor 166, accelerometer(s) 168, and/or microphone 113 (through audio circuitry 110). Information that peripherals interface 118 receives from I/O subsystem 106 includes information from touch-sensitive display 112 or a touch-sensitive surface.

In some embodiments, event monitor 171 sends requests to the peripherals interface 118 at predetermined intervals. In response, peripherals interface 118 transmits event information. In other embodiments, peripherals interface 118 transmits event information only when there is a significant event (e.g., receiving an input above a predetermined noise threshold and/or for more than a predetermined duration).

In some embodiments, event sorter 170 also includes a hit view determination module 172 and/or an active event recognizer determination module 173.

Hit view determination module 172 provides software procedures for determining where a sub-event has taken place within one or more views when touch-sensitive display 112 displays more than one view. Views are made up of controls and other elements that a user can see on the display.

Another aspect of the user interface associated with an application is a set of views, sometimes herein called application views or user interface windows, in which information is displayed and touch-based gestures occur. The application views (of a respective application) in which a touch is detected optionally correspond to programmatic levels within a programmatic or view hierarchy of the application. For example, the lowest level view in which a touch is detected is, optionally, called the hit view, and the set of events that are recognized as proper inputs are, optionally, determined based, at least in part, on the hit view of the initial touch that begins a touch-based gesture.

Hit view determination module 172 receives information related to sub-events of a touch-based gesture. When an application has multiple views organized in a hierarchy, hit view determination module 172 identifies a hit view as the lowest view in the hierarchy which should handle the sub-event. In most circumstances, the hit view is the lowest level view in which an initiating sub-event occurs (e.g., the first sub-event in the sequence of sub-events that form an event or potential event). Once the hit view is identified by the hit view determination module 172, the hit view typically receives all sub-events related to the same touch or input source for which it was identified as the hit view.

Active event recognizer determination module 173 determines which view or views within a view hierarchy should receive a particular sequence of sub-events. In some embodiments, active event recognizer determination module 173 determines that only the hit view should receive a particular sequence of sub-events. In other embodiments, active event recognizer determination module 173 determines that all views that include the physical location of a sub-event are actively involved views, and therefore determines that all actively involved views should receive a particular sequence of sub-events. In other embodiments, even if touch sub-events were entirely confined to the area associated with one particular view, views higher in the hierarchy would still remain as actively involved views.

Event dispatcher module 174 dispatches the event information to an event recognizer (e.g., event recognizer 180). In embodiments including active event recognizer determination module 173, event dispatcher module 174 delivers the event information to an event recognizer determined by active event recognizer determination module 173. In some embodiments, event dispatcher module 174 stores in an event queue the event information, which is retrieved by a respective event receiver 182.

In some embodiments, operating system 126 includes event sorter 170. Alternatively, application 136-1 includes event sorter 170. In yet other embodiments, event sorter 170 is a stand-alone module, or a part of another module stored in memory 102, such as contact/motion module 130.

In some embodiments, application 136-1 includes a plurality of event handlers 190 and one or more application views 191, each of which includes instructions for handling touch events that occur within a respective view of the application’s user interface. Each application view 191 of the application 136-1 includes one or more event recognizers 180. Typically, a respective application view 191 includes a plurality of event recognizers 180. In other embodiments, one or more of event recognizers 180 are part of a separate module, such as a user interface kit or a higher level object from which application 136-1 inherits methods and other properties. In some embodiments, a respective event handler 190 includes one or more of: data updater 176, object updater 177, GUI updater 178, and/or event data 179 received from event sorter 170. Event handler 190 optionally utilizes or calls data updater 176, object updater 177, or GUI updater 178 to update the application internal state 192. Alternatively, one or more of the application views 191 include one or more respective event handlers 190. Also, in some embodiments, one or more of data updater 176, object updater 177, and GUI updater 178 are included in a respective application view 191.

A respective event recognizer 180 receives event information (e.g., event data 179) from event sorter 170 and identifies an event from the event information. Event recognizer 180 includes event receiver 182 and event comparator 184. In some embodiments, event recognizer 180 also includes at least a subset of: metadata 183, and event delivery instructions 188 (which optionally include sub-event delivery instructions).

Event receiver 182 receives event information from event sorter 170. The event information includes information about a sub-event, for example, a touch or a touch movement. Depending on the sub-event, the event information also includes additional information, such as location of the sub-event. When the sub-event concerns motion of a touch, the event information optionally also includes speed and direction of the sub-event. In some embodiments, events include rotation of the device from one orientation to another (e.g., from a portrait orientation to a landscape orientation, or vice versa), and the event information includes corresponding information about the current orientation (also called device attitude) of the device.

Event comparator 184 compares the event information to predefined event or sub-event definitions and, based on the comparison, determines an event or sub-event, or determines or updates the state of an event or sub-event. In some embodiments, event comparator 184 includes event definitions 186. Event definitions 186 contain definitions of events (e.g., predefined sequences of sub-events), for example, event 1 (187-1), event 2 (187-2), and others. In some embodiments, sub-events in an event (187) include, for example, touch begin, touch end, touch movement, touch cancellation, and multiple touching. In one example, the definition for event 1 (187-1) is a double tap on a displayed object. The double tap, for example, comprises a first touch (touch begin) on the displayed object for a predetermined phase, a first liftoff (touch end) for a predetermined phase, a second touch (touch begin) on the displayed object for a predetermined phase, and a second liftoff (touch end) for a predetermined phase. In another example, the definition for event 2 (187-2) is a dragging on a displayed object. The dragging, for example, comprises a touch (or contact) on the displayed object for a predetermined phase, a movement of the touch across touch-sensitive display 112, and liftoff of the touch (touch end). In some embodiments, the event also includes information for one or more associated event handlers 190.

In some embodiments, event definition 187 includes a definition of an event for a respective user-interface object. In some embodiments, event comparator 184 performs a hit test to determine which user-interface object is associated with a sub-event. For example, in an application view in which three user-interface objects are displayed on touch-sensitive display 112, when a touch is detected on touch-sensitive display 112, event comparator 184 performs a hit test to determine which of the three user-interface objects is associated with the touch (sub-event). If each displayed object is associated with a respective event handler 190, the event comparator uses the result of the hit test to determine which event handler 190 should be activated. For example, event comparator 184 selects an event handler associated with the sub-event and the object triggering the hit test.

In some embodiments, the definition for a respective event (187) also includes delayed actions that delay delivery of the event information until after it has been determined whether the sequence of sub-events does or does not correspond to the event recognizer’s event type.

When a respective event recognizer 180 determines that the series of sub-events do not match any of the events in event definitions 186, the respective event recognizer 180 enters an event impossible, event failed, or event ended state, after which it disregards subsequent sub-events of the touch-based gesture. In this situation, other event recognizers, if any, that remain active for the hit view continue to track and process sub-events of an ongoing touch-based gesture.

In some embodiments, a respective event recognizer 180 includes metadata 183 with configurable properties, flags, and/or lists that indicate how the event delivery system should perform sub-event delivery to actively involved event recognizers. In some embodiments, metadata 183 includes configurable properties, flags, and/or lists that indicate how event recognizers interact, or are enabled to interact, with one another. In some embodiments, metadata 183 includes configurable properties, flags, and/or lists that indicate whether sub-events are delivered to varying levels in the view or programmatic hierarchy.

In some embodiments, a respective event recognizer 180 activates event handler 190 associated with an event when one or more particular sub-events of an event are recognized. In some embodiments, a respective event recognizer 180 delivers event information associated with the event to event handler 190. Activating an event handler 190 is distinct from sending (and deferred sending) sub-events to a respective hit view. In some embodiments, event recognizer 180 throws a flag associated with the recognized event, and event handler 190 associated with the flag catches the flag and performs a predefined process.

In some embodiments, event delivery instructions 188 include sub-event delivery instructions that deliver event information about a sub-event without activating an event handler. Instead, the sub-event delivery instructions deliver event information to event handlers associated with the series of sub-events or to actively involved views. Event handlers associated with the series of sub-events or with actively involved views receive the event information and perform a predetermined process.

In some embodiments, data updater 176 creates and updates data used in application 136-1. For example, data updater 176 updates the telephone number used in contacts module 137, or stores a video file used in video player module. In some embodiments, object updater 177 creates and updates objects used in application 136-1. For example, object updater 177 creates a new user-interface object or updates the position of a user-interface object. GUI updater 178 updates the GUI. For example, GUI updater 178 prepares display information and sends it to graphics module 132 for display on a touch-sensitive display.

In some embodiments, event handler(s) 190 includes or has access to data updater 176, object updater 177, and GUI updater 178. In some embodiments, data updater 176, object updater 177, and GUI updater 178 are included in a single module of a respective application 136-1 or application view 191. In other embodiments, they are included in two or more software modules.

It shall be understood that the foregoing discussion regarding event handling of user touches on touch-sensitive displays also applies to other forms of user inputs to operate multifunction devices 100 with input devices, not all of which are initiated on touch screens. For example, mouse movement and mouse button presses, optionally coordinated with single or multiple keyboard presses or holds; contact movements such as taps, drags, scrolls, etc. on touchpads; pen stylus inputs; movement of the device; oral instructions; detected eye movements; biometric inputs; and/or any combination thereof are optionally utilized as inputs corresponding to sub-events which define an event to be recognized.

FIG. 2 illustrates a portable multifunction device 100 having a touch screen 112 in accordance with some embodiments. The touch screen optionally displays one or more graphics within user interface (UI) 200. In this embodiment, as well as others described below, a user is enabled to select one or more of the graphics by making a gesture on the graphics, for example, with one or more fingers 202 (not drawn to scale in the figure) or one or more styluses 203 (not drawn to scale in the figure). In some embodiments, selection of one or more graphics occurs when the user breaks contact with the one or more graphics. In some embodiments, the gesture optionally includes one or more taps, one or more swipes (from left to right, right to left, upward and/or downward), and/or a rolling of a finger (from right to left, left to right, upward and/or downward) that has made contact with device 100. In some implementations or circumstances, inadvertent contact with a graphic does not select the graphic. For example, a swipe gesture that sweeps over an application icon optionally does not select the corresponding application when the gesture corresponding to selection is a tap.

Device 100 optionally also include one or more physical buttons, such as “home” or menu button 204. As described previously, menu button 204 is, optionally, used to navigate to any application 136 in a set of applications that are, optionally, executed on device 100. Alternatively, in some embodiments, the menu button is implemented as a soft key in a GUI displayed on touch screen 112.

In some embodiments, device 100 includes touch screen 112, menu button 204, push button 206 for powering the device on/off and locking the device, volume adjustment button(s) 208, subscriber identity module (SIM) card slot 210, headset jack 212, and docking/charging external port 124. Push button 206 is, optionally, used to turn the power on/off on the device by depressing the button and holding the button in the depressed state for a predefined time interval; to lock the device by depressing the button and releasing the button before the predefined time interval has elapsed; and/or to unlock the device or initiate an unlock process. In an alternative embodiment, device 100 also accepts verbal input for activation or deactivation of some functions through microphone 113. Device 100 also, optionally, includes one or more contact intensity sensors 165 for detecting intensity of contacts on touch screen 112 and/or one or more tactile output generators 167 for generating tactile outputs for a user of device 100.

FIG. 3 is a block diagram of an exemplary multifunction device with a display and a touch-sensitive surface in accordance with some embodiments. Device 300 need not be portable. In some embodiments, device 300 is a laptop computer, a desktop computer, a tablet computer, a multimedia player device, a navigation device, an educational device (such as a child’s learning toy), a gaming system, or a control device (e.g., a home or industrial controller). Device 300 typically includes one or more processing units (CPUs) 310, one or more network or other communications interfaces 360, memory 370, and one or more communication buses 320 for interconnecting these components. Communication buses 320 optionally include circuitry (sometimes called a chipset) that interconnects and controls communications between system components. Device 300 includes input/output (I/O) interface 330 comprising display 340, which is typically a touch screen display. I/O interface 330 also optionally includes a keyboard and/or mouse (or other pointing device) 350 and touchpad 355, tactile output generator 357 for generating tactile outputs on device 300 (e.g., similar to tactile output generator(s) 167 described above with reference to FIG. 1A), sensors 359 (e.g., optical, acceleration, proximity, touch-sensitive, and/or contact intensity sensors similar to contact intensity sensor(s) 165 described above with reference to FIG. 1A). Memory 370 includes high-speed random access memory, such as DRAM, SRAM, DDR RAM, or other random access solid state memory devices; and optionally includes non-volatile memory, such as one or more magnetic disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid state storage devices. Memory 370 optionally includes one or more storage devices remotely located from CPU(s) 310. In some embodiments, memory 370 stores programs, modules, and data structures analogous to the programs, modules, and data structures stored in memory 102 of portable multifunction device 100 (FIG. 1A), or a subset thereof. Furthermore, memory 370 optionally stores additional programs, modules, and data structures not present in memory 102 of portable multifunction device 100. For example, memory 370 of device 300 optionally stores drawing module 380, presentation module 382, word processing module 384, website creation module 386, disk authoring module 388, and/or spreadsheet module 390, while memory 102 of portable multifunction device 100 (FIG. 1A) optionally does not store these modules.

Each of the above-identified elements in FIG. 3 is, optionally, stored in one or more of the previously mentioned memory devices. Each of the above-identified modules corresponds to a set of instructions for performing a function described above. The above-identified modules or programs (e.g., sets of instructions) need not be implemented as separate software programs, procedures, or modules, and thus various subsets of these modules are, optionally, combined or otherwise rearranged in various embodiments. In some embodiments, memory 370 optionally stores a subset of the modules and data structures identified above. Furthermore, memory 370 optionally stores additional modules and data structures not described above.

Attention is now directed towards embodiments of user interfaces that are, optionally, implemented on, for example, portable multifunction device 100.

FIG. 4A illustrates an exemplary user interface for a menu of applications on portable multifunction device 100 in accordance with some embodiments. Similar user interfaces are, optionally, implemented on device 300. In some embodiments, user interface 400 includes the following elements, or a subset or superset thereof:

-   Signal strength indicator(s) 402 for wireless communication(s), such     as cellular and Wi-Fi signals; -   Time 404; -   Bluetooth indicator 405; -   Battery status indicator 406; -   Tray 408 with icons for frequently used applications, such as:     -   o Icon 416 for telephone module 138, labeled “Phone,” which         optionally includes an indicator 414 of the number of missed         calls or voicemail messages;     -   o Icon 418 for e-mail client module 140, labeled “Mail,” which         optionally includes an indicator 410 of the number of unread         e-mails;     -   o Icon 420 for browser module 147, labeled “Browser;” and     -   o Icon 422 for video and music player module 152, also referred         to as iPod (trademark of Apple Inc.) module 152, labeled “iPod;”         and -   Icons for other applications, such as:     -   o Icon 424 for IM module 141, labeled “Messages;”     -   o Icon 426 for calendar module 148, labeled “Calendar;”     -   o Icon 428 for image management module 144, labeled “Photos;”     -   o Icon 430 for camera module 143, labeled “Camera;”     -   o Icon 432 for online video module 155, labeled “Online Video;”     -   o Icon 434 for stocks widget 149-2, labeled “Stocks;”     -   o Icon 436 for map module 154, labeled “Maps;”     -   o Icon 438 for weather widget 149-1, labeled “Weather;”     -   o Icon 440 for alarm clock widget 149-4, labeled “Clock;”     -   o Icon 442 for workout support module 142, labeled “Workout         Support;”     -   o Icon 444 for notes module 153, labeled “Notes;” and     -   o Icon 446 for a settings application or module, labeled         “Settings,” which provides access to settings for device 100 and         its various applications 136.

It should be noted that the icon labels illustrated in FIG. 4A are merely exemplary. For example, icon 422 for video and music player module 152 is labeled “Music” or “Music Player.” Other labels are, optionally, used for various application icons. In some embodiments, a label for a respective application icon includes a name of an application corresponding to the respective application icon. In some embodiments, a label for a particular application icon is distinct from a name of an application corresponding to the particular application icon.

FIG. 4B illustrates an exemplary user interface on a device (e.g., device 300, FIG. 3 ) with a touch-sensitive surface 451 (e.g., a tablet or touchpad 355, FIG. 3 ) that is separate from the display 450 (e.g., touch screen display 112). Device 300 also, optionally, includes one or more contact intensity sensors (e.g., one or more of sensors 359) for detecting intensity of contacts on touch-sensitive surface 451 and/or one or more tactile output generators 357 for generating tactile outputs for a user of device 300.

Although some of the examples that follow will be given with reference to inputs on touch screen display 112 (where the touch-sensitive surface and the display are combined), in some embodiments, the device detects inputs on a touch-sensitive surface that is separate from the display, as shown in FIG. 4B. In some embodiments, the touch-sensitive surface (e.g., 451 in FIG. 4B) has a primary axis (e.g., 452 in FIG. 4B) that corresponds to a primary axis (e.g., 453 in FIG. 4B) on the display (e.g., 450). In accordance with these embodiments, the device detects contacts (e.g., 460 and 462 in FIG. 4B) with the touch-sensitive surface 451 at locations that correspond to respective locations on the display (e.g., in FIG. 4B, 460 corresponds to 468 and 462 corresponds to 470). In this way, user inputs (e.g., contacts 460 and 462, and movements thereof) detected by the device on the touch-sensitive surface (e.g., 451 in FIG. 4B) are used by the device to manipulate the user interface on the display (e.g., 450 in FIG. 4B) of the multifunction device when the touch-sensitive surface is separate from the display. It should be understood that similar methods are, optionally, used for other user interfaces described herein.

Additionally, while the following examples are given primarily with reference to finger inputs (e.g., finger contacts, finger tap gestures, finger swipe gestures), it should be understood that, in some embodiments, one or more of the finger inputs are replaced with input from another input device (e.g., a mouse-based input or stylus input). For example, a swipe gesture is, optionally, replaced with a mouse click (e.g., instead of a contact) followed by movement of the cursor along the path of the swipe (e.g., instead of movement of the contact). As another example, a tap gesture is, optionally, replaced with a mouse click while the cursor is located over the location of the tap gesture (e.g., instead of detection of the contact followed by ceasing to detect the contact). Similarly, when multiple user inputs are simultaneously detected, it should be understood that multiple computer mice are, optionally, used simultaneously, or a mouse and finger contacts are, optionally, used simultaneously.

FIG. 5A illustrates exemplary personal electronic device 500. Device 500 includes body 502. In some embodiments, device 500 can include some or all of the features described with respect to devices 100 and 300 (e.g., FIGS. 1A-4B). In some embodiments, device 500 has touch-sensitive display screen 504, hereafter touch screen 504. Alternatively, or in addition to touch screen 504, device 500 has a display and a touch-sensitive surface. As with devices 100 and 300, in some embodiments, touch screen 504 (or the touch-sensitive surface) optionally includes one or more intensity sensors for detecting intensity of contacts (e.g., touches) being applied. The one or more intensity sensors of touch screen 504 (or the touch-sensitive surface) can provide output data that represents the intensity of touches. The user interface of device 500 can respond to touches based on their intensity, meaning that touches of different intensities can invoke different user interface operations on device 500.

Exemplary techniques for detecting and processing touch intensity are found, for example, in related applications: International Patent Application Serial No. PCT/US2013/040061, titled “Device, Method, and Graphical User Interface for Displaying User Interface Objects Corresponding to an Application,” filed May 8, 2013, published as WIPO Publication No. WO/2013/169849, and International Patent Application Serial No. PCT/US2013/069483, titled “Device, Method, and Graphical User Interface for Transitioning Between Touch Input to Display Output Relationships,” filed Nov. 11, 2013, published as WIPO Publication No. WO/2014/105276, each of which is hereby incorporated by reference in their entirety.

In some embodiments, device 500 has one or more input mechanisms 506 and 508. Input mechanisms 506 and 508, if included, can be physical. Examples of physical input mechanisms include push buttons and rotatable mechanisms. In some embodiments, device 500 has one or more attachment mechanisms. Such attachment mechanisms, if included, can permit attachment of device 500 with, for example, hats, eyewear, earrings, necklaces, shirts, jackets, bracelets, watch straps, chains, trousers, belts, shoes, purses, backpacks, and so forth. These attachment mechanisms permit device 500 to be worn by a user.

FIG. 5B depicts exemplary personal electronic device 500. In some embodiments, device 500 can include some or all of the components described with respect to FIGS. 1A, 1B, and 3 . Device 500 has bus 512 that operatively couples I/O section 514 with one or more computer processors 516 and memory 518. I/O section 514 can be connected to display 504, which can have touch-sensitive component 522 and, optionally, intensity sensor 524 (e.g., contact intensity sensor). In addition, I/O section 514 can be connected with communication unit 530 for receiving application and operating system data, using Wi-Fi, Bluetooth, near field communication (NFC), cellular, and/or other wireless communication techniques. Device 500 can include input mechanisms 506 and/or 508. Input mechanism 506 is, optionally, a rotatable input device or a depressible and rotatable input device, for example. Input mechanism 508 is, optionally, a button, in some examples.

Input mechanism 508 is, optionally, a microphone, in some examples. Personal electronic device 500 optionally includes various sensors, such as GPS sensor 532, accelerometer 534, directional sensor 540 (e.g., compass), gyroscope 536, motion sensor 538, and/or a combination thereof, all of which can be operatively connected to I/O section 514.

Memory 518 of personal electronic device 500 can include one or more non-transitory computer-readable storage mediums, for storing computer-executable instructions, which, when executed by one or more computer processors 516, for example, can cause the computer processors to perform the techniques described below, including processes 800 and 1000 (FIGS. 8 and 10 ). A computer-readable storage medium can be any medium that can tangibly contain or store computer-executable instructions for use by or in connection with the instruction execution system, apparatus, or device. In some examples, the storage medium is a transitory computer-readable storage medium. In some examples, the storage medium is a non-transitory computer-readable storage medium. The non-transitory computer-readable storage medium can include, but is not limited to, magnetic, optical, and/or semiconductor storages. Examples of such storage include magnetic disks, optical discs based on CD, DVD, or Blu-ray technologies, as well as persistent solid-state memory such as flash, solid-state drives, and the like. Personal electronic device 500 is not limited to the components and configuration of FIG. 5B, but can include other or additional components in multiple configurations.

As used here, the term “affordance” refers to a user-interactive graphical user interface object that is, optionally, displayed on the display screen of devices 100, 300, and/or 500 (FIGS. 1A, 3, and 5A-5B). For example, an image (e.g., icon), a button, and text (e.g., hyperlink) each optionally constitute an affordance.

As used herein, the term “focus selector” refers to an input element that indicates a current part of a user interface with which a user is interacting. In some implementations that include a cursor or other location marker, the cursor acts as a “focus selector” so that when an input (e.g., a press input) is detected on a touch-sensitive surface (e.g., touchpad 355 in FIG. 3 or touch-sensitive surface 451 in FIG. 4B) while the cursor is over a particular user interface element (e.g., a button, window, slider, or other user interface element), the particular user interface element is adjusted in accordance with the detected input. In some implementations that include a touch screen display (e.g., touch-sensitive display system 112 in FIG. 1A or touch screen 112 in FIG. 4A) that enables direct interaction with user interface elements on the touch screen display, a detected contact on the touch screen acts as a “focus selector” so that when an input (e.g., a press input by the contact) is detected on the touch screen display at a location of a particular user interface element (e.g., a button, window, slider, or other user interface element), the particular user interface element is adjusted in accordance with the detected input. In some implementations, focus is moved from one region of a user interface to another region of the user interface without corresponding movement of a cursor or movement of a contact on a touch screen display (e.g., by using a tab key or arrow keys to move focus from one button to another button); in these implementations, the focus selector moves in accordance with movement of focus between different regions of the user interface. Without regard to the specific form taken by the focus selector, the focus selector is generally the user interface element (or contact on a touch screen display) that is controlled by the user so as to communicate the user’s intended interaction with the user interface (e.g., by indicating, to the device, the element of the user interface with which the user is intending to interact). For example, the location of a focus selector (e.g., a cursor, a contact, or a selection box) over a respective button while a press input is detected on the touch-sensitive surface (e.g., a touchpad or touch screen) will indicate that the user is intending to activate the respective button (as opposed to other user interface elements shown on a display of the device).

As used in the specification and claims, the term “characteristic intensity” of a contact refers to a characteristic of the contact based on one or more intensities of the contact. In some embodiments, the characteristic intensity is based on multiple intensity samples. The characteristic intensity is, optionally, based on a predefined number of intensity samples, or a set of intensity samples collected during a predetermined time period (e.g., 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10 seconds) relative to a predefined event (e.g., after detecting the contact, prior to detecting liftoff of the contact, before or after detecting a start of movement of the contact, prior to detecting an end of the contact, before or after detecting an increase in intensity of the contact, and/or before or after detecting a decrease in intensity of the contact). A characteristic intensity of a contact is, optionally, based on one or more of: a maximum value of the intensities of the contact, a mean value of the intensities of the contact, an average value of the intensities of the contact, a top 10 percentile value of the intensities of the contact, a value at the half maximum of the intensities of the contact, a value at the 90 percent maximum of the intensities of the contact, or the like. In some embodiments, the duration of the contact is used in determining the characteristic intensity (e.g., when the characteristic intensity is an average of the intensity of the contact over time). In some embodiments, the characteristic intensity is compared to a set of one or more intensity thresholds to determine whether an operation has been performed by a user. For example, the set of one or more intensity thresholds optionally includes a first intensity threshold and a second intensity threshold. In this example, a contact with a characteristic intensity that does not exceed the first threshold results in a first operation, a contact with a characteristic intensity that exceeds the first intensity threshold and does not exceed the second intensity threshold results in a second operation, and a contact with a characteristic intensity that exceeds the second threshold results in a third operation. In some embodiments, a comparison between the characteristic intensity and one or more thresholds is used to determine whether or not to perform one or more operations (e.g., whether to perform a respective operation or forgo performing the respective operation), rather than being used to determine whether to perform a first operation or a second operation.

FIG. 5C illustrates detecting a plurality of contacts 552A-552E on touch-sensitive display screen 504 with a plurality of intensity sensors 524A-524D. FIG. 5C additionally includes intensity diagrams that show the current intensity measurements of the intensity sensors 524A-524D relative to units of intensity. In this example, the intensity measurements of intensity sensors 524A and 524D are each 9 units of intensity, and the intensity measurements of intensity sensors 524B and 524C are each 7 units of intensity. In some implementations, an aggregate intensity is the sum of the intensity measurements of the plurality of intensity sensors 524A-524D, which in this example is 32 intensity units. In some embodiments, each contact is assigned a respective intensity that is a portion of the aggregate intensity. FIG. 5D illustrates assigning the aggregate intensity to contacts 552A-552E based on their distance from the center of force 554. In this example, each of contacts 552A, 552B, and 552E are assigned an intensity of contact of 8 intensity units of the aggregate intensity, and each of contacts 552C and 552D are assigned an intensity of contact of 4 intensity units of the aggregate intensity. More generally, in some implementations, each contact j is assigned a respective intensity Ij that is a portion of the aggregate intensity, A, in accordance with a predefined mathematical function, Ij = A·(Dj/ΣDi), where Dj is the distance of the respective contact j to the center of force, and ΣDi is the sum of the distances of all the respective contacts (e.g., i=1 to last) to the center of force. The operations described with reference to FIGS. 5C-5D can be performed using an electronic device similar or identical to device 100, 300, or 500. In some embodiments, a characteristic intensity of a contact is based on one or more intensities of the contact. In some embodiments, the intensity sensors are used to determine a single characteristic intensity (e.g., a single characteristic intensity of a single contact). It should be noted that the intensity diagrams are not part of a displayed user interface, but are included in FIGS. 5C-5D to aid the reader.

In some embodiments, a portion of a gesture is identified for purposes of determining a characteristic intensity. For example, a touch-sensitive surface optionally receives a continuous swipe contact transitioning from a start location and reaching an end location, at which point the intensity of the contact increases. In this example, the characteristic intensity of the contact at the end location is, optionally, based on only a portion of the continuous swipe contact, and not the entire swipe contact (e.g., only the portion of the swipe contact at the end location). In some embodiments, a smoothing algorithm is, optionally, applied to the intensities of the swipe contact prior to determining the characteristic intensity of the contact. For example, the smoothing algorithm optionally includes one or more of: an unweighted sliding-average smoothing algorithm, a triangular smoothing algorithm, a median filter smoothing algorithm, and/or an exponential smoothing algorithm. In some circumstances, these smoothing algorithms eliminate narrow spikes or dips in the intensities of the swipe contact for purposes of determining a characteristic intensity.

The intensity of a contact on the touch-sensitive surface is, optionally, characterized relative to one or more intensity thresholds, such as a contact-detection intensity threshold, a light press intensity threshold, a deep press intensity threshold, and/or one or more other intensity thresholds. In some embodiments, the light press intensity threshold corresponds to an intensity at which the device will perform operations typically associated with clicking a button of a physical mouse or a trackpad. In some embodiments, the deep press intensity threshold corresponds to an intensity at which the device will perform operations that are different from operations typically associated with clicking a button of a physical mouse or a trackpad. In some embodiments, when a contact is detected with a characteristic intensity below the light press intensity threshold (e.g., and above a nominal contact-detection intensity threshold below which the contact is no longer detected), the device will move a focus selector in accordance with movement of the contact on the touch-sensitive surface without performing an operation associated with the light press intensity threshold or the deep press intensity threshold. Generally, unless otherwise stated, these intensity thresholds are consistent between different sets of user interface figures.

An increase of characteristic intensity of the contact from an intensity below the light press intensity threshold to an intensity between the light press intensity threshold and the deep press intensity threshold is sometimes referred to as a “light press” input. An increase of characteristic intensity of the contact from an intensity below the deep press intensity threshold to an intensity above the deep press intensity threshold is sometimes referred to as a “deep press” input. An increase of characteristic intensity of the contact from an intensity below the contact-detection intensity threshold to an intensity between the contact-detection intensity threshold and the light press intensity threshold is sometimes referred to as detecting the contact on the touch-surface. A decrease of characteristic intensity of the contact from an intensity above the contact-detection intensity threshold to an intensity below the contact-detection intensity threshold is sometimes referred to as detecting liftoff of the contact from the touch-surface. In some embodiments, the contact-detection intensity threshold is zero. In some embodiments, the contact-detection intensity threshold is greater than zero.

In some embodiments described herein, one or more operations are performed in response to detecting a gesture that includes a respective press input or in response to detecting the respective press input performed with a respective contact (or a plurality of contacts), where the respective press input is detected based at least in part on detecting an increase in intensity of the contact (or plurality of contacts) above a press-input intensity threshold. In some embodiments, the respective operation is performed in response to detecting the increase in intensity of the respective contact above the press-input intensity threshold (e.g., a “down stroke” of the respective press input). In some embodiments, the press input includes an increase in intensity of the respective contact above the press-input intensity threshold and a subsequent decrease in intensity of the contact below the press-input intensity threshold, and the respective operation is performed in response to detecting the subsequent decrease in intensity of the respective contact below the press-input threshold (e.g., an “up stroke” of the respective press input).

FIGS. 5E-5H illustrate detection of a gesture that includes a press input that corresponds to an increase in intensity of a contact 562 from an intensity below a light press intensity threshold (e.g., “IT_(L)”) in FIG. 5E, to an intensity above a deep press intensity threshold (e.g., “IT_(D)”) in FIG. 5H. The gesture performed with contact 562 is detected on touch-sensitive surface 560 while cursor 576 is displayed over application icon 572B corresponding to App 2, on a displayed user interface 570 that includes application icons 572A-572D displayed in predefined region 574. In some embodiments, the gesture is detected on touch-sensitive display 504. The intensity sensors detect the intensity of contacts on touch-sensitive surface 560. The device determines that the intensity of contact 562 peaked above the deep press intensity threshold (e.g., “IT_(D)”). Contact 562 is maintained on touch-sensitive surface 560. In response to the detection of the gesture, and in accordance with contact 562 having an intensity that goes above the deep press intensity threshold (e.g., “IT_(D)”) during the gesture, reduced-scale representations 578A-578C (e.g., thumbnails) of recently opened documents for App 2 are displayed, as shown in FIGS. 5F-5H. In some embodiments, the intensity, which is compared to the one or more intensity thresholds, is the characteristic intensity of a contact. It should be noted that the intensity diagram for contact 562 is not part of a displayed user interface, but is included in FIGS. 5E-5H to aid the reader.

In some embodiments, the display of representations 578A-578C includes an animation. For example, representation 578A is initially displayed in proximity of application icon 572B, as shown in FIG. 5F. As the animation proceeds, representation 578A moves upward and representation 578B is displayed in proximity of application icon 572B, as shown in FIG. 5G. Then, representations 578A moves upward, 578B moves upward toward representation 578A, and representation 578C is displayed in proximity of application icon 572B, as shown in FIG. 5H. Representations 578A-578C form an array above icon 572B. In some embodiments, the animation progresses in accordance with an intensity of contact 562, as shown in FIGS. 5F-5G, where the representations 578A-578C appear and move upwards as the intensity of contact 562 increases toward the deep press intensity threshold (e.g., “IT_(D)”). In some embodiments, the intensity, on which the progress of the animation is based, is the characteristic intensity of the contact. The operations described with reference to FIGS. 5E-5H can be performed using an electronic device similar or identical to device 100, 300, or 500.

In some embodiments, the device employs intensity hysteresis to avoid accidental inputs sometimes termed “jitter,” where the device defines or selects a hysteresis intensity threshold with a predefined relationship to the press-input intensity threshold (e.g., the hysteresis intensity threshold is X intensity units lower than the press-input intensity threshold or the hysteresis intensity threshold is 75%, 90%, or some reasonable proportion of the press-input intensity threshold). Thus, in some embodiments, the press input includes an increase in intensity of the respective contact above the press-input intensity threshold and a subsequent decrease in intensity of the contact below the hysteresis intensity threshold that corresponds to the press-input intensity threshold, and the respective operation is performed in response to detecting the subsequent decrease in intensity of the respective contact below the hysteresis intensity threshold (e.g., an “up stroke” of the respective press input). Similarly, in some embodiments, the press input is detected only when the device detects an increase in intensity of the contact from an intensity at or below the hysteresis intensity threshold to an intensity at or above the press-input intensity threshold and, optionally, a subsequent decrease in intensity of the contact to an intensity at or below the hysteresis intensity, and the respective operation is performed in response to detecting the press input (e.g., the increase in intensity of the contact or the decrease in intensity of the contact, depending on the circumstances).

For ease of explanation, the descriptions of operations performed in response to a press input associated with a press-input intensity threshold or in response to a gesture including the press input are, optionally, triggered in response to detecting either: an increase in intensity of a contact above the press-input intensity threshold, an increase in intensity of a contact from an intensity below the hysteresis intensity threshold to an intensity above the press-input intensity threshold, a decrease in intensity of the contact below the press-input intensity threshold, and/or a decrease in intensity of the contact below the hysteresis intensity threshold corresponding to the press-input intensity threshold. Additionally, in examples where an operation is described as being performed in response to detecting a decrease in intensity of a contact below the press-input intensity threshold, the operation is, optionally, performed in response to detecting a decrease in intensity of the contact below a hysteresis intensity threshold corresponding to, and lower than, the press-input intensity threshold.

Attention is now directed towards embodiments of user interfaces (“UI”) and associated processes that are implemented on an electronic device, such as portable multifunction device 100, device 300, or device 500.

FIGS. 6A-6D illustrate an exemplary technique for applying simulated lighting to an image with depth information, in accordance with some embodiments. The technique illustrated in these figures is used in the processes described below, including the processes in FIGS. 8 and 10 .

FIG. 6A illustrates an image of a face 602. When the image of the face 602 is captured, depth information corresponding to face 602 is captured with the image data. In some embodiments, depth information corresponding to face 602 is captured using one or more depth camera sensors (e.g., 175). Depth camera sensors receive data from the environment to create a three dimensional model of face 602.

FIG. 6B illustrates a three dimensional model 604 of face 602. Three dimensional model 604 is based on the depth information captured with the image data of face 602. In some embodiments, three dimensional model 604 is based on a depth map (e.g., depth map image) of face 602. A depth map (e.g., depth map image) contains information (e.g., values) that relates to the distance of objects in a scene (e.g., face 602) from a viewpoint (e.g., a camera, an optical sensor, a depth camera sensor). In one embodiment of a depth map, each depth pixel defines the position in the viewpoint’s Z-axis where its corresponding two-dimensional pixel is located. In some embodiments, a depth map is composed of pixels wherein each pixel is defined by a value (e.g., 0 - 255). For example, the “0” value represents pixels that are located at the most distant place in a “three dimensional” scene and the “255” value represents pixels that are located closest to a viewpoint (e.g., a camera, an optical sensor, a depth camera sensor) in the “three dimensional” scene. In other embodiments, a depth map represents the distance between an object in a scene (e.g., face 602) and the plane of the viewpoint. In some embodiments, the depth map includes information about the relative depth of various features of an object of interest in view of the depth camera (e.g., the relative depth of eyes, nose, mouth, ears of a user’s face). In some embodiments, the depth map includes information that enables the device to determine contours of the object of interest in a z direction.

FIG. 6C illustrates simulated lighting being applied to three dimensional model 604. Simulated lighting is applied by positioning simulated light sources 606 a, 606 b, and 606 c around three dimensional model 604. While shown with three simulated light sources, simulated lighting can be applied to three dimensional model 604 using various numbers of simulated light sources, such as one, two, or four or more. Simulated light sources 606 a, 606 b, and 606 c cast light on three dimensional model 604 based on their position and direction relative to three dimensional model 604. In some embodiments, simulated light sources 606 a, 606 b, and 606 c have brightness and color characteristics that effect the simulated lighting applied to three dimensional model 604.

When simulated lighting is applied to three dimensional model 604, the contours of the model cause the level of simulated lighting appearing on different portions of the model to vary. For example, simulated light source 606 a positioned on the left side of three dimensional model 604 causes light to be cast primarily on the left side of three dimensional model 604 while less light is cast on the right side of three dimensional model 604. Furthermore, certain contours of three dimensional model 604 cause shadows to be cast on portions of three dimensional model 604 based on the position and direction of a simulated light source. For example, simulated light source 606 b positioned below three dimensional model 604 causes the nose and cheekbones of three dimensional model 604 to cast shadows on other portions of three dimensional model 604.

Using the three dimensional model 604 of face 602, simulated lighting is applied to face 602, as shown in FIG. 6D. In FIG. 6D, the simulated lighting applied to face 602 appears to be emitted from a simulated light source located at simulated light source icon 608. Based on how light emitted from that location casts light and shadows on three dimensional model 604, face 602 is displayed with different levels of lighting on different portion of the face (e.g., the lighting of the three dimensional model 604 is mapped to face 602). Furthermore, using the depth information associated with the image of face 602, the face 602 is isolated from the background of the image (e.g., the original background is replaced with a black background). This allows the face 602 to be displayed with simulated lighting independently of the background, and/or allows face 602 to be displayed in front of different backgrounds.

FIGS. 7A-7J illustrate exemplary user interfaces for displaying an image with depth information, in accordance with some embodiments. The user interfaces in these figures are used to illustrate the processes described below, including the processes in FIG. 8 .

FIGS. 7A-7C illustrates an electronic device 700 including a display 702 (e.g., integrated with a touch-sensitive surface). In some embodiments, electronic device 700 includes one or more features of device 100, 300, or 500. Electronic device 700 displays, on display 702, a user interface 704 (e.g., an image viewer user interface). An image 706 is displayed in user interface 704. In some embodiments, image 706 is a portrait including a face of a person. In some embodiments, image 706 includes depth information corresponding to the face of the person. The depth information is captured with the image data for image 706 using one or more depth camera sensors (e.g., 175). In some embodiments, the depth information is a depth map (e.g., depth map image). A depth map (e.g., depth map image) contains information (e.g., values) that relates to the distance of objects in a scene (e.g., the face of the person) from a viewpoint (e.g., a camera, an optical sensor, a depth camera sensor). In one embodiment of a depth map, each depth pixel defines the position in the viewpoint’s Z-axis where its corresponding two-dimensional pixel is located. In some embodiments, a depth map is composed of pixels wherein each pixel is defined by a value (e.g., 0 - 255). For example, the “0” value represents pixels that are located at the most distant place in a “three dimensional” scene and the “255” value represents pixels that are located closest to a viewpoint (e.g., a camera, an optical sensor, a depth camera sensor) in the “three dimensional” scene. In other embodiments, a depth map represents the distance between an object in a scene (e.g., the face of the person) and the plane of the viewpoint. In some embodiments, the depth map includes information about the relative depth of various features of an object of interest in view of the depth camera (e.g., the relative depth of eyes, nose, mouth, ears of the face of the person). In some embodiments, the depth map includes information that enables the device to determine contours of the object of interest in a z direction.

As shown in FIGS. 7A-7C, image 706 is displayed using a reveal animation. The reveal animation includes displaying image 706 with varying levels and/or sources of simulated lighting. Image 706 is displayed with simulated lighting using the techniques described in reference to FIGS. 6A-6D. In some embodiments, image 706 is displayed using the reveal animation shown in FIGS. 7A-7C in response to a request to view image 706 (e.g., in response to image 706 being selected from a photo album of the electronic device 700).

At the beginning of the reveal animation (as shown in FIG. 7A), image 706 is displayed with low levels of simulated lighting (e.g., the face of the person in image 706 is dimly lit). In some embodiments, different portions of image 706 are lit with different levels of simulated lighting, due to the contours of the face of the person in image 706 (e.g., a first portion of the face is displayed with a first level of simulated lighting while a second portion of the face is displayed with a second, different level of simulated lighting). As the animation progresses (as shown in FIGS. 7B and 7C), image 706 is displayed with progressively greater levels of simulated lighting (e.g., the face of the person in image 706 appears brighter). In some embodiments, as the animation progresses, different portions of image 706 are lit with different levels of simulated lighting, due to the contours of the face of the person in image 706 and a perceived motion of simulated light source(s) during the reveal animation. In some embodiments, the simulated lighting is applied to image 706 during the reveal animation such that the face of the person in image 706 appears to emerge from darkness (e.g., a perceived position of a simulated light source moves during the reveal animation to appear as if the person steps underneath the simulated light source). In some embodiments, the simulated lighting is applied to image 706 during the reveal animation such that a simulated light source appears to move horizontally and/or vertically onto the face of the person in image 706 (e.g., the face of the person in image 706 appears to be lit with light from a flashlight or spotlight moving onto the face during the reveal animation).

In some embodiments, at the end of the reveal animation (as shown in FIG. 7C), image 706 is displayed with simulated lighting that substantially recreates the original lighting of image 706 (e.g., the natural lighting that was originally captured in the image data for image 706). In some embodiments, at the end of the reveal animation (as shown in FIG. 7C), the original image 706 is displayed without simulated lighting.

In some embodiments, at the end of the reveal animation (as shown in FIG. 7C), image 706 is displayed with simulated lighting based on a respective (e.g., current) time of day (e.g., brightness, color, angle with respect to subject are modified based on the time of day (e.g., less light on subject at night time). In some embodiments, time of day corresponds to the current time of electronic device 700 displaying image 706. In some embodiments, time of day corresponds to the current time where the person in image 706 is currently located. In some embodiments, time of day corresponds to the current time where image 706 was captured.

In some embodiments, at the end of the reveal animation (as shown in FIG. 7C), image 706 is displayed with simulated lighting based on a current weather information (e.g., less light on subject when cloudy). In some embodiments, the weather corresponds to current weather where electronic device 700 is located. In some embodiments, the weather corresponds to current weather where the person in image 706 is currently located. In some embodiments, the weather corresponds to the current weather where image 706 was captured. In some embodiments, the overall lighting at the end of the reveal animation (as shown in FIG. 7C) is based on one or more properties of the lighting at the time the image was captured (e.g., brightness, color, angle with respect to subject) combined with the current weather information.

FIG. 7D illustrates electronic device 700 displaying lock-screen interface 708. Lock-screen interface 708 includes image 706 and time 710. As shown in FIG. 7D, image 706 is displayed overlaying a portion of time 710. As described in reference to FIGS. 6A-6D, based on depth information of image 706, the face of the person in image 706 can be separated from the background of image 706. This allows the face of the person in image 706 to overlay different backgrounds (e.g., time 710).

In some embodiments, when lock-screen interface 708 is displayed (e.g., when electronic device 700 wakes from a low-power (e.g., sleep) state), image 706 is displayed using the reveal animation described in reference to FIGS. 7A-7C. The left drawing of FIG. 7D illustrates lock-screen interface 708 at the beginning of the reveal animation (e.g., image 706 is displayed with a low level of simulated lighting). The right drawing of FIG. 7D illustrates lock-screen interface 708 at the end of the reveal animation (e.g., image 706 is displayed with a greater level of simulated lighting).

In some embodiments, image 706 is displayed in lock-screen interface 708 using the reveal animation in response to an unlocking of electronic device 700. For example, image 706 is initially displayed in lock-screen interface 708 with a low level of simulated lighting (as shown in the left drawing of FIG. 7D). Image 706 continues to be displayed with the low level of simulated lighting in lock-screen interface 708 until electronic device 700 is unlocked (e.g., until an authorized user is detected, such as through facial recognition or fingerprint recognition). When electronic device 700 is unlocked, the reveal animation proceeds, as described in reference to FIGS. 7A-7C. After the reveal animation ends (e.g., after image 706 is displayed with a greater level simulated lighting as shown in the right drawing of FIG. 7D), an unlocked user interface is displayed (such as shown in FIG. 4A).

FIG. 7E illustrates electronic device 700 displaying incoming call interface 712. Incoming call interface 712 includes image 706, accept affordance 714, and decline affordance 716. As shown in FIG. 7E, accept affordance 714 and decline affordance 716 are shown overlaying image 706.

In some embodiments, when incoming call interface 712 is displayed (e.g., when a request to join a telephone call is detected), image 706 is displayed using the reveal animation described in reference to FIGS. 7A-7C. In some embodiments, image 706 is associated with a user sending the request to join the telephone call (e.g., the person in image 706 is the person calling electronic device 700). The left drawing of FIG. 7E illustrates incoming call interface 712 at the beginning of the reveal animation (e.g., image 706 is displayed with a low level of simulated lighting). The right drawing of FIG. 7E illustrates incoming call interface 712 at the end of the reveal animation (e.g., image 706 is displayed with a greater level of simulated lighting). In some embodiments, the image 706 as displayed at the end of the reveal animation continues to be displayed until an input on the accept affordance 714 or decline affordance 716 is detected, or until the incoming call interface 712 otherwise ceases to be displayed (e.g., the request to join the telephone call times out).

In some embodiments, image 706 is displayed in incoming call interface 712 using the reveal animation in response to detecting an input (e.g., a finger contact) on accept affordance 714. For example, image 706 is initially displayed in incoming call interface 712 with a low level of simulated lighting (as shown in the left drawing of FIG. 7E). Image 706 continues to be displayed with the low level of simulated lighting in incoming call interface 712 until an input (e.g., a finger contact) is detected on accept affordance 714. When the input is detected on accept affordance 714, the reveal animation proceeds, as described in reference to FIGS. 7A-7C. After the reveal animation ends, an active call interface is displayed. In some embodiments, image 706 continues to be displayed with the higher level of simulated lighting (e.g., as shown in the right drawing of FIG. 7E) in the active call interface while the telephone call is active.

FIGS. 7F-7I illustrate a photo viewing interface 718. In some embodiments, when image 706 is selected to be viewed in the photo viewing interface 718 (e.g., when image 706 is selected from a photo album of electronic device 700), image 706 is displayed with the reveal animation, as described in reference to FIGS. 7A-7C.

After the reveal animation, image 706 is displayed in photo viewing interface 718 as shown in FIG. 7F. In some embodiments, image 706 is displayed in photo viewing interface 718 with simulated lighting that substantially recreates the original lighting of image 706 (e.g., the natural lighting that was originally captured in the image data for image 706) (e.g., amount of light, color of the light, direction(s) of source(s) of light). In some embodiments, image 706 is displayed in photo viewing interface 718 with simulated lighting that corresponds to one or more simulated light source(s) in fixed position(s).

While image 706 is displayed in photo viewing interface 718, a swipe input 703 (e.g., a finger contact moving in left/right direction) is detected on image 706, as shown in FIGS. 7F-7G. In response to detecting the swipe input 703, image 706 is animated moving in a direction off of display 702 based on the direction of the swipe input 703. For example, a swipe input 703 in a left direction results in image 706 moving to the left off of the edge of display 702, as shown in FIGS. 7G-7H. As image 706 moves off of display 702, image 706 is displayed with varying levels of simulated lighting. In some embodiments, image 706 is displayed with simulated lighting such that one or more simulated light source(s) appear to be in fixed position(s) as image 706 moves.

In some embodiments, as image 706 moves off of display 702, a second image 720 moves onto display 702 in the same direction of movement, as shown in FIGS. 7G-7I. As image 720 moves onto display 702, image 720 is displayed with varying levels of simulated lighting. In some embodiments, image 720 is displayed such that image 720 appears to be lit with the same simulated light source(s) as image 706 (e.g., the one or more simulated light source(s) remain in the same fixed position(s) as image 720 moves onto display 702).

FIG. 7J illustrates image 720 displayed in photo viewing interface 718. In some embodiments, image 720 is selected to be viewed in photo viewing interface 718 (e.g., image 720 is selected from a photo album of electronic device 700). In response to selecting image 720 for viewing, image 720 is displayed with the reveal animation, as described in reference to FIGS. 7A-7C. In some embodiments, image 720 is displayed in photo viewing interface 718 in response to a swipe input on another photo displayed in photo viewing interface 718, as described in reference to FIGS. 7F-7I.

In some embodiments, image 720 is displayed with simulated lighting that corresponds to one or more simulated light source(s) in fixed position(s). While image 720 is displayed, a change in orientation of electronic device 700 is detected (e.g., using a gyroscope and/or accelerometer). In some embodiments, in response to the change in orientation of electronic device 700, image 720 is displayed with different simulated lighting, as shown in FIG. 7J, such that the one or more simulated light source(s) appear to remain in fixed position(s) as the orientation of electronic device 700 changes. In some embodiments, in response to the change in orientation of electronic device 700, image 720 is displayed with different simulated lighting such that the one or more simulated light source(s) appear to change position(s) based on the change in orientation of electronic device 700 (e.g., the position(s) of the simulated light source(s) is based on the orientation of electronic device 700).

FIG. 8 is a flow diagram illustrating a method for displaying an image with depth information using an electronic device in accordance with some embodiments. Method 800 is performed at an electronic device (e.g., 100, 300, 500, 700, 900) with a display (e.g., 702). Some operations in method 800 are, optionally, combined, the orders of some operations are, optionally, changed, and some operations are, optionally, omitted.

As described below, method 800 provides an intuitive way for displaying an image with depth information. The method reduces the cognitive burden on a user for recognizing the subject of an image, thereby creating a more efficient human-machine interface. For battery-operated computing devices, enabling a user to recognize the subject of an image faster and more efficiently conserves power and increases the time between battery charges.

Electronic device (e.g., 700) receives (802) a request to display an image (e.g., 706) that includes a subject (e.g., an authorized user of the device or another person who is the subject of the image). Image data associated with the image includes depth information associated with the subject.

In response (804) to the request, electronic device displays (806) a first modified image on the display (e.g., the first frame of a reveal animation, such as shown in FIG. 7A). Displaying the first modified image includes displaying, based on the depth information, a first level of simulated lighting on a first portion of the subject and a second level of simulated lighting on a second portion of the subject, the first level being greater than the second level. For example, one side of the subject’s face is lit with a dim simulated light source, while the other side of the subject’s face appears to be in shadow.

Further in response (804) to the request, and subsequent to displaying the first modified image, the electronic device (e.g., 700) displays (808) a second modified image (e.g., the second frame of a reveal animation, such as shown in FIG. 7B). Displaying the second modified image includes displaying, based on the depth information, a third level of simulated lighting on the first portion of the subject and a fourth level of simulated lighting on the second portion of the subject, the fourth level being greater than the second level. For example, the simulated light source appears brighter and/or appears to move toward the center of the subject’s face. Displaying an image with simulated lighting improves visual feedback by enabling a user to more easily recognize the subject of the image (e.g., by emphasizing the contours of the subject’s face). Providing improved visual feedback to the user enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.

In accordance with some embodiments, the depth information is obtained during a biometric enrollment process wherein one or more portions of the subject’s face are captured for purposes of biometric authentication. In some embodiments, the image data includes at least two components: an RGB component that encodes the visual characteristics of a captured image, and depth data that encodes information about the relative spacing relationship of elements within the captured image (e.g., the depth data encodes that a user is in the foreground, and background elements, such as a tree positioned behind the user, are in the background). In some embodiments, the depth data is a depth map. In some embodiments, a depth map (e.g., depth map image) contains information (e.g., values) that relates to the distance of objects in a scene from a viewpoint (e.g., a camera). In some examples of a depth map, each depth pixel defines the position in the viewpoint’s Z-axis where its corresponding two-dimensional pixel is located. In some examples, a depth map is composed of pixels wherein each pixel is defined by a value (e.g., 0 - 255). For example, the “0” value represents pixels that are located at the most distant place in a “three dimensional” scene and the “255” value represents pixels that are located closest to a viewpoint (e.g., camera) in the “three dimensional” scene. In other examples, a depth map represents the distance between an object in a scene and the plane of the viewpoint. In some embodiments, the depth map includes information about the relative depth of various features of an object of interest in view of the depth camera (e.g., the relative depth of eyes, nose, mouth, ears of a user’s face). In some embodiments, the depth map includes information that enables the device to determine contours of the object of interest in a z direction. In some embodiments, the depth data has a second depth component (e.g., a second portion of depth data that encodes a spatial position of the background in the camera display region; a plurality of depth pixels that form a discrete portion of the depth map, such as a background), separate from the first depth component, the second depth aspect including the representation of the background in the camera display region. In some embodiments, the first depth aspect and second depth aspect are used to determine a spatial relationship between the subject in the camera display region and the background in the camera display region. This spatial relationship can be used to distinguish the subject from the background. This distinction can be exploited to, for example, apply different visual effects (e.g., visual effects having a depth component) to the subject and background.

In accordance with some embodiments, the first portion of the subject corresponds to content of the image at a first depth (e.g., an eye socket) and the second portion of the subject corresponds to content of the image at a second depth (e.g., a cheekbone).

In accordance with some embodiments, the third level of simulated lighting is less than the first level of simulated lighting. For example, the first portion of the subject appears less bright as the second portion appears brighter, such as when the simulated light source pans or rotates from the side of the subject’s face toward the center of the subject’s face.

In accordance with some embodiments, the third level of simulated lighting is greater than the first level of simulated lighting (e.g., all portions of the subject appear brighter in the second modified image).

In accordance with some embodiments, the request to display the image is received in response to the electronic device exiting a low power mode (e.g., when a phone wakes from a sleep mode, such as shown in FIG. 7D).

In accordance with some embodiments, the request to display the image is received in response to the electronic device detecting biometric information associated with an authorized user (e.g., detecting the face of an authorized user).

In accordance with some embodiments, displaying the first modified image (e.g., 706, as shown in FIG. 7A) further includes displaying the subject in front of one or more graphical elements (e.g., lock icon, notifications, time, date, etc.) (e.g., 710) associated with a lock screen of the electronic device.

In accordance with some embodiments, the request to display the image is received in response to receiving a communication (e.g., phone call, instant message, video chat, such as shown in FIG. 7E) from the subject of the image. Displaying an image with simulated lighting when receiving a communication from the subject of the image improves visual feedback by enabling a user to more easily recognize the subject of the image (e.g., by emphasizing the contours of the subject’s face). Providing improved visual feedback to the user enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.

In accordance with some embodiments, the request to display the image is received in response to an input selecting the image for viewing (e.g., tapping on a thumbnail of the image in a photo gallery).

In accordance with some embodiments, while displaying the second modified image (e.g., 706, as shown in FIG. 7B), electronic device (e.g., 700) detects (810) an input (e.g., 703) on the touch-sensitive display (e.g., 702) at a location corresponding to the second modified image (e.g., 706). The input includes movement in a first direction.

In accordance with some embodiments, in response to the input, the electronic device (e.g., 700) displays (812) a third modified image (e.g., 706, such as shown in FIG. 7G) with the subject in a different location on the touch-sensitive display than the subject in the second modified image based on the first direction of the movement. Displaying the third modified image includes displaying, based on the depth information, a fifth level of simulated lighting on the first portion of the subject and a sixth level of simulated lighting on the second portion of the subject, the fifth level and sixth level being based on the first direction of the movement. For example, light appears to be emitted from a stationary light source as subject of photo moves across screen in response to a swipe input or the light changes angle or distance relative to the subject as the swipe gesture proceeds.

In accordance with some embodiments, in response to the input, the electronic device (e.g., 700) displays at least a portion of a second image (e.g., 720) on the touch-sensitive display (e.g., 702). The second image (e.g., 720) includes a second subject and second image data associated with the second image includes second depth information associated with the second subject. In some embodiments, displaying at least the portion of the second image includes displaying, based on the second depth information, a seventh level of simulated lighting on a first portion of the second subject and a eighth level of simulated lighting on a second portion of the second subject, the seventh level and eighth level being based on the first direction of the movement (e.g., 720, such as shown in FIG. 7H). For example, simulated lighting is applied to the next photo in a camera roll as it slides onto the display, where the simulated lighting appears to be emitted from the stationary light source. In some embodiments, the seventh level of simulated lighting is the same as the first, second, third, fourth, fifth, or sixth levels of simulated lighting. In accordance with some embodiments, the eighth level of simulated lighting is the same as the first, second, third, fourth, fifth, or sixth levels of simulated lighting. Displaying the second image with simulated lighting improves visual feedback by enabling a user to more easily recognize the subject of the second image (e.g., by emphasizing the contours of the subject’s face). Providing improved visual feedback to the user enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.

In accordance with some embodiments, the electronic device (e.g., 700) includes an orientation sensor (e.g., accelerometer 168, gyroscope). While displaying the second modified image, the electronic device detects a change in orientation of the electronic device. In response to detecting the change in orientation, the electronic device displays a fourth modified image (e.g., 720, such as shown in FIG. 7J). Displaying the fourth modified image optionally includes displaying, based on the depth information, a ninth level of simulated lighting on the first portion of the subject and a tenth level of simulated lighting on the second portion of the subject, the ninth level and tenth level being based on the change in orientation of the electronic device (e.g., location of simulated light source is moved relative to the subject of the photo based on tilt of the device).

In accordance with some embodiments, after displaying the second modified image, the electronic device (e.g., 700) displays a fifth modified image (e.g., 706, as shown in FIG. 7C). Displaying the fifth modified image optionally includes displaying, based on lighting information determined from the image data (e.g., information representing the original lighting conditions (e.g., amount of light, color of the light, direction(s) of source(s) of light) at the time the image was taken), an eleventh level of simulated lighting on the first portion of the subject and a twelfth level of simulated lighting on the second portion of the subject. The eleventh level corresponds to an original level of lighting of the first portion of the subject and the twelfth level corresponds to an original level of lighting of the second portion of the subject (e.g., simulated lighting aligns with original lighting of the photo.) In some examples, the overall lighting is based on one or more properties of the lighting at the time the photo was taken combined with other user input. In some examples, the top/bottom angle of the simulated light source is determined based on the original lighting of the photo at the time it was taken while the left/right angle of the simulated light source is determined based on user input (e.g., swiping), or vice versa.

In accordance with some embodiments, after displaying the second modified image, the electronic device (e.g., 700) displays a sixth modified image (e.g., 706, as shown in FIG. 7C). Displaying the sixth modified image optionally includes displaying, based on the depth information, a thirteenth level of simulated lighting on the first portion of the subject and a fourteenth level of simulated lighting on the second portion of the subject. The thirteenth level and fourteenth level are optionally based on a respective (e.g., current) time of day e.g., brightness, color, angle with respect to subject are modified based on the time of day (e.g., less light on subject at night time). In some embodiments, time of day corresponds to current time of the device viewing the photo or current time where the subject of the photo is located. Displaying an image with simulated lighting corresponding to a time of day improves visual feedback by enabling a user to quickly and easily recognize the time of day. Providing improved visual feedback to the user enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.

In accordance with some embodiments, after displaying the second modified image, the electronic device (e.g., 700) displays a seventh modified image. Displaying the seventh modified image optionally includes displaying, based on the depth information, a fifteenth level of simulated lighting on the first portion of the subject and a sixteenth level of simulated lighting on the second portion of the subject. The fifteenth level and sixteenth level are optionally based on a current weather information (e.g., less light on subject when cloudy). In some embodiments, the weather corresponds to current weather where the electronic device displaying the photo is located, or current weather where the subject of the photo is located. In some embodiments, the overall lighting is based on one or more properties of the lighting at the time the photo was taken (e.g., brightness, color, angle with respect to subject) combined with the current weather information. Displaying an image with simulated lighting corresponding to the current weather improves visual feedback by enabling a user to quickly and easily recognize the current weather. Providing improved visual feedback to the user enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.

Note that details of the processes described above with respect to method 800 (e.g., FIG. 8 ) are also applicable in an analogous manner to the methods described below. For example, method 1000 optionally includes one or more of the characteristics of the various methods described above with reference to method 800. For example, simulated lighting effects can be applied to an image during editing of the image. For brevity, these details are not repeated below.

FIGS. 9A-9K illustrate exemplary user interfaces for editing an image with depth information, in accordance with some embodiments. The user interfaces in these figures are used to illustrate the processes described below, including the processes in FIG. 10 .

FIG. 9A illustrates an electronic device 900 including a display 902 (e.g., integrated with a touch-sensitive surface). In some embodiments, electronic device 700 includes one or more features of device 100, 300, or 500. In some embodiments, electronic device 900 is electronic device 700. Electronic device 900 displays, on display 902, a user interface 904 for editing an image 906. Image 906 includes a foreground element 908 a (e.g., a person) and a background element 908 b (e.g., a wall). In some embodiments, image 906 includes depth information corresponding to the scene captured in image 906. The depth information is captured with the image data for image 906 using one or more depth camera sensors (e.g., 175). In some embodiments, the depth information is a depth map (e.g., depth map image). A depth map (e.g., depth map image) contains information (e.g., values) that relates to the distance of objects in a scene (e.g., foreground element 908 a, background element 908 b) from a viewpoint (e.g., a camera, an optical sensor, a depth camera sensor). In one embodiment of a depth map, each depth pixel defines the position in the viewpoint’s Z-axis where its corresponding two-dimensional pixel is located. In some embodiments, a depth map is composed of pixels wherein each pixel is defined by a value (e.g., 0 - 255). For example, the “0” value represents pixels that are located at the most distant place in a “three dimensional” scene and the “255” value represents pixels that are located closest to a viewpoint (e.g., a camera, an optical sensor, a depth camera sensor) in the “three dimensional” scene. In other embodiments, a depth map represents the distance between an object in a scene (e.g., foreground element 908 a, background element 908 b) and the plane of the viewpoint. In some embodiments, the depth map includes information about the relative depth of various features of an object of interest in view of the depth camera (e.g., the relative depth of eyes, nose, mouth, ears of a person). In some embodiments, the depth map includes information that enables the device to determine contours of the object of interest in a z direction.

While displaying image 906 in user interface 904, an input 903 (e.g., a finger contact) is detected at a location on image 906 corresponding to background element 908 b. Using the depth information associated with image 906, a depth range corresponding to the location of input 903 is determined.

As shown in FIG. 9B, in response to detecting input 903, a graphical object 910 (e.g., text) is inserted into image 906 at a depth corresponding to the depth range of input 903. Elements in image 906 with a shallower depth (e.g., foreground element 908 a) than the depth range of input 903 are displayed in front of inserted graphical object 910, while elements in image 906 with a deeper depth (e.g., background element 908 b) than the depth range of input 903 are displayed behind inserted graphical object 910. In this way, graphical object 910 appears to be an element present within the captured scene of image 906.

In some embodiments, a simulated depth effect (e.g., a visual effect having a depth component) is applied to the inserted graphical object 910. The simulated depth effect is associated with a focal plane of the depth range of input 903 such that the inserted graphical object 910 appears with a similar focus as other elements in the depth range (e.g., the inserted graphical object 910 is visually modified to have a different degree of blurriness/sharpness, size, degree of brightness, degree of saturation, and/or degree of shape-distortion in order to simulate a depth effect, such as a bokeh effect). In some embodiments, the simulated depth effect is “simulated” in that the effect is generated (e.g., artificially generated) based on a manipulation of the underlying image data for the graphical object 910 to create and apply the effect to the graphical object 910 (e.g., as opposed to being a “natural” effect that is based on underlying data as originally captured via one or more cameras based on the optical properties of light passing through one or more lenses to reach the image sensor of the camera).

In some embodiments, the location of inserted graphical object 910 is modified in response to detecting a change in orientation (e.g., with an accelerometer and/or gyroscope) of the electronic device 900. For example, the location of inserted graphical object 910 can be modified as the orientation of electronic device 900 changes to create a parallax between graphical object 910 and other elements of image 906.

As shown in FIG. 9C, in response to detecting input 903 on background element 908 b (as shown in FIG. 9A), a skewed graphical object 912 (e.g., skewed text) is inserted into image 906 to align with the surface of background element 908 b.

As shown in FIG. 9D, while displaying image 906 in user interface 904, an input 905 (e.g., a finger contact) is detected at a location on image 906 corresponding to foreground element 908 a. Using the depth information associated with image 906, a depth range corresponding to the location of input 905 is determined.

As shown in FIG. 9E, in response to detecting input 905, a simulated light source is inserted into image 906 at a depth corresponding to the depth range of input 905 (e.g., at the depth of foreground element 908 a). As a result of inserting the simulated light source, foreground element 908 a is displayed with simulated lighting (e.g., the face of the person in image 906 is lit with simulated lighting) (e.g., as described in reference to FIGS. 6A-6D). In some embodiments, different levels of simulated lighting are applied to different portions of foreground element 908 a based on depth information associated with foreground element 908 a (e.g., a first portion of the face is displayed with a first level of simulated lighting while a second portion of the face is displayed with a second, different level of simulated lighting due to the contours of the face of the person in image 906).

In some embodiments, the simulated light source is initially positioned to substantially recreate the original lighting of image 906 (e.g., the natural lighting that was originally captured in the image data for image 906) (e.g., amount of light, color of the light, direction(s) of source(s) of light).

In some embodiments, the simulated lighting corresponds to a predetermined lighting style (e.g., the simulated lighting source changes location over time in a predefined pattern, multiple simulated lighting sources are positioned at predefined locations, and/or additional filter effects applied to image 906).

A position of the simulated light source is indicated by light icon 914. In some embodiments, the size of light icon 914 further indicates the intensity (e.g., brightness) of the simulated light source. In some embodiments, the horizontal/vertical position (e.g., x/y position) of the simulated light source is changed in response to input 907 moving light icon 914 to a different location. In some embodiments, input 907 is also associated with a characteristic intensity. In some embodiments, an intensity of the simulated light source (e.g., brightness) is changed based on the characteristic intensity of input 907. In some embodiments, a depth of the simulated light source (e.g., z position) is changed based on the characteristic intensity of input 907.

In some embodiments, input 907 is also associated with a duration. In some embodiments, an intensity of the simulated light source (e.g., brightness) is changed based on the duration of input 907.

As shown in FIG. 9F, the horizontal/vertical position (e.g., x/y position) of light icon 914 is changed in response to input 907 shown in FIG. 9E. As the position of the simulated light source changes, foreground element 908 a is displayed with different simulated lighting corresponding to the changing position of the simulated light source. Furthermore, as shown in FIG. 9F, the intensity of the simulated light source (e.g., brightness) is changed in response to input 907, as indicated be the reduced size of light icon 914. In some embodiments, the intensity of the simulated light source (e.g., brightness) is changed based on a characteristic intensity of input 907 (e.g., a light press results in less brightness, a deep press results in more brightness). In some embodiments, the intensity of the simulated light source (e.g., brightness) is changed based on the duration of input 907 (e.g., short press results in less brightness, long press results in more brightness).

As shown in FIG. 9G, an input 909 is detected on light icon 914. In response to input 909 a depth of the simulated light source (e.g., z position) associated with light icon 914 is changed based on a characteristic intensity of input 909 (e.g., the simulated light source is pushed to a deeper depth range of image 906).

As shown in FIG. 9H, a graphical object 916 (e.g., text) is inserted into image 906 at a depth corresponding to the depth range of input 905 (e.g., at the depth of foreground element 908 a). In some embodiments, inserted graphical object 916 is a simulated light source (e.g., light appears to be emitted by graphical object 916). In response to inserting graphical object 916, foreground element 908 a is displayed with simulated lighting (e.g., the face of the person in image 906 is lit with simulated lighting) (e.g., as described in reference to FIGS. 6A-6D). In some embodiments, different levels of simulated lighting are applied to different portions of foreground element 908 a based on depth information associated with foreground element 908 a (e.g., a first portion of the face is displayed with a first level of simulated lighting while a second portion of the face is displayed with a second, different level of simulated lighting due to the contours of the face of the person in image 906).

In some embodiments, simulated lighting is applied to the inserted graphical object 916 (e.g., the lighting of the inserted graphical object is based on position(s) of one or more light source(s) (real or simulated) in image 906 and relative positions of other elements in the image (e.g., other elements cast shadows on the inserted graphical object 916)).

As shown in FIG. 9I, in response to input 905 on foreground element 908 a, an option 918 is displayed to modify one or more visual characteristics of foreground element 908 a (e.g., brightness, saturation, contrast) without modifying visual characteristics of other elements in image 906. In some embodiments, when one or more visual characteristics of foreground element 908 a are modified, an indication 920 (e.g., outline, glowing effect) is displayed to indicate foreground element 908 a has been modified.

As shown in FIG. 9J, in response to input 905 on foreground element 908 a, a face 922 of foreground element 908 a is identified. Face 922 is identified based in part on depth information associated with image 906. After face 922 is identified, face 922 is separated from other elements of image 906. In some embodiments, after face 922 is separated from other elements of image 906, face 922 is used as a graphical object (e.g., a sticker) in other applications of electronic device 900.

FIG. 9K illustrates electronic device 900 displaying an instant messaging interface 924. Instant messaging interface includes an option for inserting stickers into an instant messaging conversation. As shown in FIG. 9K, face 922 from image 906 (shown in FIG. 9J) is included as a sticker for insertion in the instant messaging conversation.

FIG. 10 is a flow diagram illustrating a method for editing an image with depth information using an electronic device in accordance with some embodiments. Method 1000 is performed at an electronic device (e.g., 100, 300, 500, 700, 900) with a display (e.g., 902). Some operations in method 1000 are, optionally, combined, the orders of some operations are, optionally, changed, and some operations are, optionally, omitted.

As described below, method 1000 provides an intuitive way for editing an image with depth information. The method reduces the cognitive burden on a user for editing the image, thereby creating a more efficient human-machine interface. For battery-operated computing devices, enabling a user to edit an image faster and more efficiently conserves power and increases the time between battery charges.

Electronic device (e.g., 900) displays (1002), on the display (e.g., 902), an image (e.g., 906) (e.g., a photograph or video) including a plurality of elements (e.g., 908 a, 908 b). The plurality of elements are associated with depth information that specifies different depths for different elements in the plurality of elements. In some embodiments, the depth information is obtained with a depth sensor used in conjunction with a camera of the electronic device. In some embodiments, the depth information is determined based on image data from multiple cameras using parallax to generate a depth map.

In accordance with some embodiments, the display (e.g., 902) is a touch-sensitive display. Optionally, prior to receiving a request (e.g., 1004) to edit a portion of the image (e.g., 906), the electronic device (e.g., 900) receives (1012) an input at a location on the touch-sensitive display corresponding to the portion of the image. The electronic device identifies (1014) an object in the image (e.g., 908 a) associated the location for editing. The identified object is an element of the plurality of elements in a first depth range.

In accordance with some embodiments, the electronic device (e.g., 900) isolates the identified object (e.g., 922) from one or more (e.g., all remaining) other elements in the image (e.g., 908 a, 908 b). The electronic device displays the isolated object separately from (e.g., as a cut out, in isolation without displaying the one or more other elements) the one or more other of elements in the image. In some examples, the object (e.g., 922) is displayed and edited independently of the rest of the image (e.g., as a sticker in an instant messaging application, such as shown in FIG. 9K).

While displaying the image on the display (e.g., 902), the electronic device (e.g., 900) receives (1004) a request (e.g., 905, 907) to edit a portion of the image. For example, the electronic device receives an input instructing how the image is to be edited (e.g., dragging a slider after selecting a particular person to apply a color filter to that person or increase/decrease saturation of that person).

In response to receiving the request (e.g., 905, 907) to edit the portion of the image, the electronic device (e.g., 900) modifies (1006), based on the depth information, visual characteristics of one or more elements (e.g., a wall, a face, a location in space (e.g., where text is to be inserted)) of the plurality of elements in the first depth range (e.g., a range of distances (e.g., 2-4 feet) from the camera used to the capture the image) without modifying visual characteristics of elements that are not in (e.g., that are outside of) the first depth range. Modifying visual characteristics in a selected depth range without modifying visual characteristics outside the selected depth range allows a user to edit an image more efficiently. Performing an optimized operation without requiring further user input enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.

In accordance with some embodiments, the image data for the image (e.g., 906) includes at least two components: an RGB component that encodes the visual characteristics of a captured image, and depth data that encodes information about the relative spacing relationship of elements within the captured image (e.g., the depth data encodes that a user is in the foreground, and background elements, such as a tree positioned behind the user, are in the background). In accordance with some embodiments, the depth data is a depth map. In some embodiments, a depth map (e.g., depth map image) contains information (e.g., values) that relates to the distance of objects in a scene from a viewpoint (e.g., a camera). In some embodiments of a depth map, each depth pixel defines the position in the viewpoint’s Z-axis where its corresponding two-dimensional pixel is located. In some examples, a depth map is composed of pixels wherein each pixel is defined by a value (e.g., 0 - 255). For example, the “0” value represents pixels that are located at the most distant place in a “three dimensional” scene and the “255” value represents pixels that are located closest to a viewpoint (e.g., camera) in the “three dimensional” scene. In other examples, a depth map represents the distance between an object in a scene and the plane of the viewpoint. In some embodiments, the depth map includes information about the relative depth of various features of an object of interest in view of the depth camera (e.g., the relative depth of eyes, nose, mouth, ears of a user’s face). In some embodiments, the depth map includes information that enables the electronic device to determine contours of the object of interest in a z direction. In some embodiments, the depth data has a second depth component (e.g., a second portion of depth data that encodes a spatial position of the background in the camera display region; a plurality of depth pixels that form a discrete portion of the depth map, such as a background), separate from the first depth component. The second depth aspect includes the representation of the background in the camera display region. In some embodiments, the first depth aspect and second depth aspect are used to determine a spatial relationship between the subject in the camera display region and the background in the camera display region. The electronic device optionally uses this spatial relationship to distinguish the subject from the background. This distinction can be exploited to, for example, apply different visual effects (e.g., visual effects having a depth component) to the subject and background.

In accordance with some embodiments, after modifying the visual characteristic of the one or more elements of the plurality of elements in the first depth range and while displaying the image (e.g., 906) on the display (e.g., 902), the electronic device (e.g., 900) receives (1008) a second request (e.g., 905) to edit a second portion (e.g., 908 a) of the image (e.g., an input instructing how the image is to be edited). In some examples, the electronic device receives input dragging a slider while a particular person is selected to apply a color filter to that person or increase/decrease saturation of that person.

In accordance with some embodiments, in response to receiving the second request to edit the second portion of the image, the electronic device (e.g., 900) modifies (1010), based on the depth information, visual characteristics of one or more second elements (e.g., a wall, a face, a location in space (e.g., where text is to be inserted)) of the plurality of elements in a second depth range without modifying visual characteristics of elements that are not in (e.g., that are outside of) the second depth range. Modifying visual characteristics in a selected depth range without modifying visual characteristics outside the selected depth range allows a user to edit an image more efficiently. Performing an optimized operation without requiring further user input enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.

In accordance with some embodiments, modifying the visual characteristics of the one or more elements in the first depth range includes modifying one or more of brightness, saturation, or contrast of the one or more elements without modifying the brightness, saturation, or contrast of elements not in the first depth range.

In accordance with some embodiments, after modifying the visual characteristics of the one or more elements, the electronic device (e.g., 900) displays an indication (e.g., 920) associated with the modification (e.g., outline or glowing effect around a modified element).

In accordance with some embodiments, modifying the visual characteristics of the one or more elements in the first depth range includes applying simulated lighting to the one or more elements (e.g., 908 a) in the first depth range (e.g., as shown in FIG. 9E). In some embodiments, an initial location of the simulated lighting source aligns with the location of original light source of the image (e.g., information representing the original lighting conditions (e.g., amount of light, color of the light, direction(s) of source(s) of light) at the time the image was taken).

In accordance with some embodiments, the request to edit the portion of the image (e.g., 906) includes a touch input (e.g., 907) on a touch-sensitive surface. The level of simulated lighting applied to the one or more elements is based on one or more characteristics of the touch input (e.g., duration or characteristic intensity of the touch input changes the level of simulated lighting).

In accordance with some embodiments, the display (e.g., 902) is a touch-sensitive display and the request to edit the portion of the image includes a touch input (e.g., 907) on the touch-sensitive display corresponding to a location in the image. The simulated lighting is applied to the one or more elements based on the location of the touch input (e.g., the source of the simulated lighting appears to be at the location). In some embodiments, the source of the simulated lighting is moved to different locations by dragging the touch input to different locations of the display (e.g., as shown in FIG. 9E).

In accordance with some embodiments, the display (e.g., 902) is a touch-sensitive display and the request to edit the portion of the image includes a touch input (e.g., 909) on the touch-sensitive display with a characteristic intensity (e.g., the electronic device detects a touch input and the touch input has a characteristic intensity). The simulated lighting is applied to the one or more elements based on the characteristic intensity of the touch input. In some embodiments, the source of the simulated lighting appears to at a depth associated with the characteristic intensity of the touch input. In some embodiments, the source of the simulated lighting is moved to forward or backward in depth by changing the intensity of the touch input. In some embodiments, the amount of movement of the simulated light is determined based on the magnitude of the intensity of the touch input and/or the duration for which the intensity of the touch input is maintained at a particular level of intensity (e.g., the simulated light moves back farther as the intensity increases and/or as the intensity is maintained over a threshold intensity for a period of time and/or the simulated light moves forward as the intensity decreases and/or as the intensity is maintained below the threshold intensity for a period of time).

In accordance with some embodiments, the electronic device (e.g., 900) displays an indication (e.g., 914) (e.g., light or sun icon) of a one or more characteristics (e.g., location, intensity) of a simulated source of the simulated lighting. In some embodiments, the indication (e.g., 914) also indicates the brightness level of the simulated lighting (e.g., with the size of the icon, brightness of the icon, or additional visual elements). Displaying an indication of a simulated light source improves visual feedback by enabling a user to quickly and easily recognize location and brightness of the simulated light source. Providing improved visual feedback to the user enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.

In accordance with some embodiments, the simulated lighting corresponds to a predetermined lighting style (e.g., the simulated light source(s) for the simulated lighting changes location over time in a predefined pattern, the simulated light source(s) includes multiple simulated light sources at predefined locations, and/or additional filter effects are applied to the image).

In accordance with some embodiments, modifying the visual characteristics of the one or more elements in the first depth range includes inserting a graphical object (e.g., 910, 912, 916) (e.g., text) into the image at the first depth range. In some embodiments, the graphical object is displayed in front of elements at deeper depth and behind elements at shallower depths. In some embodiments, such as with video, the inserted graphical object optionally appears to remain stationary as the camera moves (e.g., inserted text appears to be fixed to a location in the image). Inserting a graphical object in a selected depth range allows a user to edit an image more efficiently. Performing an optimized operation without requiring further user input enhances the operability of the device and makes the user-device interface more efficient (e.g., by helping the user to provide proper inputs and reducing user mistakes when operating/interacting with the device) which, additionally, reduces power usage and improves battery life of the device by enabling the user to use the device more quickly and efficiently.

In accordance with some embodiments, the inserted graphical object (e.g., 910, 912) is obstructed by at least one element (e.g., 908 a) not in the first depth range (e.g., the inserted graphical object appears behind an element at a shallower depth). In some embodiments, a second graphical object is inserted to appear in front of the element obstructing the other graphical object. For example, text is optionally inserted to appear behind and in front of a person in the image.

In accordance with some embodiments, simulated lighting is applied (e.g., by the electronic device 900) to the inserted graphical object (e.g., 910, 912, 916). In some examples, the lighting of the inserted graphical object is based on location(s) of light source(s) (real or simulated) in the image and relative positions of other elements in the image (e.g., other elements cast shadows on the inserted graphical object).

In accordance with some embodiments, simulated lighting applied to one or more elements in the image (e.g., 906) is affected by the inserted graphical object (e.g., 916) in the image. In some embodiments, the lighting of other elements in the image is modified based on light or shadows cast by the inserted graphical object. In some embodiments, the inserted graphical object is a source for simulated lighting (e.g., as shown in FIG. 9H).

In accordance with some embodiments, a simulated depth effect (e.g., a visual effect having a depth component) is applied (e.g., by electronic device 900) to the inserted graphical object. The simulated depth effect is associated with a focal plane of the first depth range such that the inserted graphical object (e.g., 910, 912, 916) appears with a similar focus as other elements in the first depth range (e.g., the inserted graphical object is visually modified to have a different degree of blurriness/sharpness, size, degree of brightness, degree of saturation, and/or degree of shape-distortion in order to simulate a depth effect, such as a bokeh effect). In some embodiments, the simulated depth effect is “simulated” in that the effect is generated (e.g., artificially generated) based on a manipulation of the underlying image data for the graphical object to create and apply the effect to the graphical object (e.g., as opposed to being a “natural” effect that is based on underlying data as originally captured via one or more cameras based on the optical properties of light passing through one or more lenses to reach the image sensor of the camera).

In accordance with some embodiments, the electronic device (e.g., 900) identifies an object (e.g., 908 b) (e.g., a wall) in the image at the first depth range. The graphical object (e.g., 912) is inserted to align with a surface of the object in the image (e.g., inserted text is angled to appear on the surface of the wall).

In accordance with some embodiments, the electronic device (e.g., 900) includes an orientation sensor (e.g., accelerometer 168, gyroscope). The electronic device detects a change in orientation of the electronic device. The electronic device modifies a location of the inserted graphical object (e.g., 910, 916) relative to the other elements of the image based on the change in orientation (e.g., a parallax effect occurs when changing the viewing angle of the device).

Note that details of the processes described above with respect to method 1000 (e.g., FIG. 10 ) are also applicable in an analogous manner to the methods described above. For example, method 800 optionally includes one or more of the characteristics of the various methods described above with reference to method 1000. For example, after an image is displayed with simulated lighting effects, the image can be edited. For brevity, these details are not repeated above.

The foregoing description, for purpose of explanation, has been described with reference to specific embodiments. However, the illustrative discussions above are not intended to be exhaustive or to limit the invention to the precise forms disclosed. Many modifications and variations are possible in view of the above teachings. The embodiments were chosen and described in order to best explain the principles of the techniques and their practical applications. Others skilled in the art are thereby enabled to best utilize the techniques and various embodiments with various modifications as are suited to the particular use contemplated.

Although the disclosure and examples have been fully described with reference to the accompanying drawings, it is to be noted that various changes and modifications will become apparent to those skilled in the art. Such changes and modifications are to be understood as being included within the scope of the disclosure and examples as defined by the claims.

As described above, one aspect of the present technology is the gathering and use of data available from various sources to display and edit images. The present disclosure contemplates that in some instances, this gathered data may include personal information data that uniquely identifies or can be used to contact or locate a specific person. Such personal information data can include demographic data, location-based data, telephone numbers, email addresses, twitter IDs, home addresses, data or records relating to a user’s health or level of fitness (e.g., vital signs measurements, medication information, exercise information), date of birth, or any other identifying or personal information.

The present disclosure recognizes that the use of such personal information data, in the present technology, can be used to the benefit of users. For example, the personal information data can be used to recognize a person or subject within a displayed image. Accordingly, use of such personal information data enables users to more easily recognize the person or subject in the image. Further, other uses for personal information data that benefit the user are also contemplated by the present disclosure. For instance, health and fitness data may be used to provide insights into a user’s general wellness, or may be used as positive feedback to individuals using technology to pursue wellness goals.

The present disclosure contemplates that the entities responsible for the collection, analysis, disclosure, transfer, storage, or other use of such personal information data will comply with well-established privacy policies and/or privacy practices. In particular, such entities should implement and consistently use privacy policies and practices that are generally recognized as meeting or exceeding industry or governmental requirements for maintaining personal information data private and secure. Such policies should be easily accessible by users, and should be updated as the collection and/or use of data changes. Personal information from users should be collected for legitimate and reasonable uses of the entity and not shared or sold outside of those legitimate uses. Further, such collection/sharing should occur after receiving the informed consent of the users. Additionally, such entities should consider taking any needed steps for safeguarding and securing access to such personal information data and ensuring that others with access to the personal information data adhere to their privacy policies and procedures. Further, such entities can subject themselves to evaluation by third parties to certify their adherence to widely accepted privacy policies and practices. In addition, policies and practices should be adapted for the particular types of personal information data being collected and/or accessed and adapted to applicable laws and standards, including jurisdiction-specific considerations. For instance, in the US, collection of or access to certain health data may be governed by federal and/or state laws, such as the Health Insurance Portability and Accountability Act (HIPAA); whereas health data in other countries may be subject to other regulations and policies and should be handled accordingly. Hence different privacy practices should be maintained for different personal data types in each country.

Despite the foregoing, the present disclosure also contemplates embodiments in which users selectively block the use of, or access to, personal information data. That is, the present disclosure contemplates that hardware and/or software elements can be provided to prevent or block access to such personal information data. For example, in the case of recognition of a person or subject within an image, the present technology can be configured to allow users to select to “opt in” or “opt out” of participation in the collection of personal information data during registration for services or anytime thereafter. In addition to providing “opt in” and “opt out” options, the present disclosure contemplates providing notifications relating to the access or use of personal information. For instance, a user may be notified upon downloading an app that their personal information data will be accessed and then reminded again just before personal information data is accessed by the app.

Moreover, it is the intent of the present disclosure that personal information data should be managed and handled in a way to minimize risks of unintentional or unauthorized access or use. Risk can be minimized by limiting the collection of data and deleting data once it is no longer needed. In addition, and when applicable, including in certain health related applications, data de-identification can be used to protect a user’s privacy. De-identification may be facilitated, when appropriate, by removing specific identifiers (e.g., date of birth, etc.), controlling the amount or specificity of data stored (e.g., collecting location data a city level rather than at an address level), controlling how data is stored (e.g., aggregating data across users), and/or other methods.

Therefore, although the present disclosure broadly covers use of personal information data to implement one or more various disclosed embodiments, the present disclosure also contemplates that the various embodiments can also be implemented without the need for accessing such personal information data. That is, the various embodiments of the present technology are not rendered inoperable due to the lack of all or a portion of such personal information data. For example, images can be displayed or edited based on non-personal information data or a bare minimum amount of personal information, such as the content being requested by the device associated with a user, other non-personal information available to the device, or publicly available information. 

What is claimed is:
 1. An electronic device, comprising: a display; one or more processors; and memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for: displaying, via the display, an image in a first application, wherein the image includes a plurality of elements, and wherein the plurality of elements are associated with depth information that specifies different depths for different elements in the plurality of elements; while displaying the image via the display, receiving an input at a location corresponding to a portion of the image; identifying an object in the image associated with the location of the input, wherein the identified object includes one or more elements of the plurality of elements in a first depth range; isolating the identified object from one or more other elements in the image; displaying the isolated object separately from the one or more other elements in the image; and utilizing the isolated object in a second application different from the first application.
 2. The electronic device of claim 1, wherein the one or more other elements in the image are outside of the first depth range.
 3. The electronic device of claim 1, wherein utilizing the isolated object in the second application includes displaying the isolated object in the second application without the one or more other elements in the image.
 4. The electronic device of claim 1, wherein the second application is a messaging application.
 5. The electronic device of claim 1, wherein utilizing the isolated object in the second application includes inserting the isolated object into a messaging conversation.
 6. The electronic device of claim 1, wherein the isolated object is a face.
 7. The electronic device of claim 1, wherein the one or more programs further include instructions for: receiving a request to edit a portion of the isolated object; and in response to receiving the request to edit the portion of the isolated object, modifying, based on the depth information, visual characteristics of the one or more elements of the plurality of elements in the first depth range without modifying visual characteristics of elements that are not in the first depth range.
 8. The electronic device of claim 7, wherein modifying the visual characteristics of the one or more elements in a first depth range includes modifying one or more of brightness, saturation, or contrast of the one or more elements without modifying the brightness, saturation, or contrast of elements not in the first depth range.
 9. The electronic device of claim 7, wherein the one or more programs further include instructions for: after modifying the visual characteristics of the one or more elements, displaying an indication associated with the modification.
 10. A non-transitory computer-readable storage medium storing one or more programs configured to be executed by one or more processors of an electronic device with a display, the one or more programs including instructions for: displaying, via the display, an image in a first application, wherein the image includes a plurality of elements, and wherein the plurality of elements are associated with depth information that specifies different depths for different elements in the plurality of elements; while displaying the image via the display, receiving an input at a location corresponding to a portion of the image; identifying an object in the image associated with the location of the input, wherein the identified object includes one or more elements of the plurality of elements in a first depth range; isolating the identified object from one or more other elements in the image; displaying the isolated object separately from the one or more other elements in the image; and utilizing the isolated object in a second application different from the first application.
 11. A method, comprising: at an electronic device with a display: displaying, via the display, an image in a first application, wherein the image includes a plurality of elements, and wherein the plurality of elements are associated with depth information that specifies different depths for different elements in the plurality of elements; while displaying the image via the display, receiving an input at a location corresponding to a portion of the image; identifying an object in the image associated with the location of the input, wherein the identified object includes one or more elements of the plurality of elements in a first depth range; isolating the identified object from one or more other elements in the image; displaying the isolated object separately from the one or more other elements in the image; and utilizing the isolated object in a second application different from the first application. 